From: Florian Weimer <fw@deneb.enyo.de>
To: Greg KH <gregkh@suse.de>
Cc: Matthew Keenan <matt@opcode-solutions.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org
Subject: Re: Linux 2.6.22.18
Date: Tue, 12 Feb 2008 18:48:42 +0100 [thread overview]
Message-ID: <878x1q6p6t.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20080211154512.GA26178@suse.de> (Greg KH's message of "Mon, 11 Feb 2008 07:45:12 -0800")
* Greg KH:
> the logic is a little different in 2.6.22 and earlier in regards to this
> area of code. This way we are safer.
Your patch doesn't include the CVE-2006-0010 hunk. Is this because
get_user() implies an access_ok() check (while __copy_from_user()
obviously does not)?
next prev parent reply other threads:[~2008-02-12 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 7:43 Greg Kroah-Hartman
2008-02-11 7:43 ` Greg Kroah-Hartman
2008-02-11 11:31 ` Matthew Keenan
2008-02-11 15:45 ` Greg KH
2008-02-12 17:48 ` Florian Weimer [this message]
2008-02-12 17:50 ` Greg KH
2008-02-11 16:32 ` Linus Torvalds
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=878x1q6p6t.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@opcode-solutions.com \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®