From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Dirty COW bug
Date: Fri, 21 Oct 2016 19:22:11 +0300 [thread overview]
Message-ID: <CAJ1xhMXute9pFphMCX9uBMUAXEJScyi2h8UU+2MnAWedeHhZRg@mail.gmail.com> (raw)
In-Reply-To: <CAHVfhufX1nJp=K9VX1yMUb4-Fsu32DXw6aUNm68qarpb=xXLbQ@mail.gmail.com>
On Fri, Oct 21, 2016 at 6:42 PM, Andy Mender <andymenderunix@gmail.com> wrote:
> On 21 October 2016 at 17:04, Rich Freeman <rich0@gentoo.org> wrote:
>>
>> On Fri, Oct 21, 2016 at 10:49 AM, Mick <michaelkintzios@gmail.com> wrote:
>> > https://github.com/dirtycow/dirtycow.github.io/wiki/VulnerabilityDetails
>> >
>> > Are we patched? I'm running 4.4.21-gentoo
>> >
>>
>> Not yet:
>> https://bugs.gentoo.org/show_bug.cgi?id=597624
>>
>> You're probably going to want to update to 4.4.26. It has been
>> released, though it doesn't look like it is packaged in Gentoo yet.
>> I've been running upstream's git for a while (currently on 4.4.26).
>>
>> --
>> Rich
>>
> Would a Gentoo .config work with the upstream "vanilla" 4.4.26 kernel?
> I know Gentoo does some patching to the upstream sources and menuconfig has
> additional features thereby.
>
> ~ Andy
Running 'make oldconfig' within the sources directory by default uses
whatever config-x.y.z is the highest version available in /boot.
Otherwise, copying the config file desired to the sources directory
followed by running 'make oldconfig' will generate a new one based on
the config file copied.
You could than run the diff on the gentoo config file and the vanilla
one and take it from there.
next prev parent reply other threads:[~2016-10-21 16:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 14:49 [gentoo-user] Dirty COW bug Mick
2016-10-21 15:04 ` Rich Freeman
2016-10-21 15:42 ` Andy Mender
2016-10-21 16:22 ` Alexander Kapshuk [this message]
2016-10-21 17:39 ` Rich Freeman
2016-10-21 18:02 ` Mick
2016-10-21 18:11 ` Rich Freeman
2016-10-22 11:25 ` Nils Freydank
2016-10-22 8:04 ` J. Roeleveld
2016-10-22 10:52 ` Rich Freeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ1xhMXute9pFphMCX9uBMUAXEJScyi2h8UU+2MnAWedeHhZRg@mail.gmail.com \
--to=alexander.kapshuk@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox