From: Andrew Morton <akpm@linux-foundation.org>
To: Greg KH <greg@kroah.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] [patch] fuse: fix permission checking
Date: Sat, 23 Feb 2008 11:22:51 -0800 [thread overview]
Message-ID: <20080223112251.f797c4b6.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080223190859.GB8641@kroah.com>
On Sat, 23 Feb 2008 11:08:59 -0800 Greg KH <greg@kroah.com> wrote:
> On Sat, Feb 23, 2008 at 10:38:59AM +0100, Miklos Szeredi wrote:
> > > On Fri, Feb 15, 2008 at 11:23:47AM +0100, Miklos Szeredi wrote:
> > > > This is for 2.6.25 and 2.6.24.y, but NOT for 2.6.23.y.
> > > >
> > > > Thanks,
> > > > Miklos
> > > > ----
> > > >
> > > > From: Miklos Szeredi <mszeredi@suse.cz>
> > > >
> > > > I added a nasty local variable shadowing bug to fuse in 2.6.24, with
> > > > the result, that the 'default_permissions' mount option is basically
> > > > ignored.
> > >
> > > When this goes into Linus's tree, can you let us know along with the git
> > > commit id?
> >
> > I'd really like to see this in 2.6.24.3. How much time is left?
> > Should I bypass Andrew and submit to Linus ASAP?
>
> There will be a .24.4 soon afterward (week or so), so don't feel like
> you have to rush. Unless this is some kind of security issue?
>
I'll be sending a bunch of fixes to Linus this weekend, including this patch.
next prev parent reply other threads:[~2008-02-23 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 10:23 [patch] fuse: fix permission checking Miklos Szeredi
2008-02-15 20:35 ` Harvey Harrison
2008-02-22 23:19 ` [stable] " Greg KH
2008-02-23 9:38 ` Miklos Szeredi
2008-02-23 19:08 ` Greg KH
2008-02-23 19:22 ` Andrew Morton [this message]
2008-02-23 19:40 ` Miklos Szeredi
2008-02-25 10:45 ` Miklos Szeredi
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=20080223112251.f797c4b6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stable@kernel.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