From: Greg KH <greg@kroah.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Driver-Core: devtmpfs - reset inode permissions before unlinking
Date: Fri, 15 Jan 2010 19:31:41 -0800 [thread overview]
Message-ID: <20100116033141.GB15306@kroah.com> (raw)
In-Reply-To: <20100116022641.GF3814@khazad-dum.debian.net>
On Sat, Jan 16, 2010 at 12:26:41AM -0200, Henrique de Moraes Holschuh wrote:
> On Thu, 14 Jan 2010, Kay Sievers wrote:
> > > That said, this does fix a possible security problem when a misconfigured
> > > system is used, and the fix looks rather simple... ?Can it go to -stable
> > > eventually, even if it is months in the future, after it gets some testing
> > > in .34 ? ? Minor problems are still problems...
> >
> > Sure, we could do that. There is some stuff in the current .33 kernel,
> > which could go into .32-stable too, if that's useful.
>
> I think it probably would be useful. I understand .32 is going to stay with
> us for a long time, so it should get any fixes that have withstood the test
> of time.
>
> It is very annoying to have subtly different kernel behaviour (from
> mainline) in a long-term stable series...
I've queued up this patch to go into the -stable trees. Any other
specific one you can think of should also go?
thanks,
greg k-h
next prev parent reply other threads:[~2010-01-16 3:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 13:16 Driver-Core: devtmpfs - reset inode permissions before unlinking Kay Sievers
2010-01-14 3:49 ` Greg KH
2010-01-14 5:11 ` Kay Sievers
2010-01-14 20:53 ` Henrique de Moraes Holschuh
2010-01-14 20:59 ` Kay Sievers
2010-01-14 21:07 ` Henrique de Moraes Holschuh
2010-01-14 21:45 ` Kay Sievers
2010-01-16 2:26 ` Henrique de Moraes Holschuh
2010-01-16 3:31 ` Greg KH [this message]
2010-01-17 3:33 ` Henrique de Moraes Holschuh
2010-01-14 21:00 ` Henrique de Moraes Holschuh
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=20100116033141.GB15306@kroah.com \
--to=greg@kroah.com \
--cc=hmh@hmh.eng.br \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).