From: Greg KH <greg@kroah.com>
To: Duane Griffin <duaneg@dghda.com>
Cc: Chuck Ebbert <cebbert@redhat.com>,
npiggin@suse.de, Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] patch remove-broken-ptrace-special-case-code-from-file-mapping.patch queued to -stable tree
Date: Fri, 2 Nov 2007 11:00:04 -0700 [thread overview]
Message-ID: <20071102180004.GA22849@kroah.com> (raw)
In-Reply-To: <e9e943910711021052j4b5366c4u8b3ae87080e8b310@mail.gmail.com>
On Fri, Nov 02, 2007 at 05:52:25PM +0000, Duane Griffin wrote:
> On 02/11/2007, Chuck Ebbert <cebbert@redhat.com> wrote:
> > On 11/02/2007 12:58 PM, Greg KH wrote:
> > > Unless Nick really objects, and then I'll drop yours and use his, but I
> > > don't think that Duane verified that his patch fixed the issue.
> > >
> >
> > I put Nick's in Fedora, so it had better work... ;)
>
> I've tested both patches, and they both fix the problem. So no
> worries, either way :)
>
> As Linus said, his patch does change the behaviour. I'm not qualified
> to judge how risky that is, however I think that the change is an
> improvement. In fact in my original bug report I suggested the old
> behaviour could be considered buggy and the new behaviour might be
> preferable.
Ok, thanks for letting me know. I'll stick with Linus's patch for now,
unless someone really complains :)
thanks,
greg k-h
prev parent reply other threads:[~2007-11-02 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071102162222.EC46D14540CB@imap.suse.de>
[not found] ` <alpine.LFD.0.999.0711020945330.3342@woody.linux-foundation.org>
[not found] ` <20071102165816.GA16493@suse.de>
2007-11-02 17:09 ` patch remove-broken-ptrace-special-case-code-from-file-mapping.patch queued to -stable tree Chuck Ebbert
2007-11-02 17:52 ` Duane Griffin
2007-11-02 18:00 ` Greg KH [this message]
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=20071102180004.GA22849@kroah.com \
--to=greg@kroah.com \
--cc=cebbert@redhat.com \
--cc=duaneg@dghda.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--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