From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Driver-Core: devtmpfs - reset inode permissions before unlinking
Date: Thu, 14 Jan 2010 06:11:16 +0100 [thread overview]
Message-ID: <ac3eb2511001132111t7ac93f97xe1e54d93e3a43b02@mail.gmail.com> (raw)
In-Reply-To: <20100114034909.GB27634@kroah.com>
On Thu, Jan 14, 2010 at 04:49, Greg KH <greg@kroah.com> wrote:
> On Wed, Jan 13, 2010 at 02:16:36PM +0100, Kay Sievers wrote:
>> From: Kay Sievers <kay.sievers@vrfy.org>
>> Subject: Driver-Core: devtmpfs - reset inode permissions before unlinking
>>
>> Before unlinking the inode, reset the current permissions of possible
>> references like hardlinks, so granted permissions can not be retained
>> across the device lifetime by creating hardlinks, in the unusual case
>> that there is a user-writable directory on the same filesystem.
>
> Is this something that we need to worry about for existing users
> (2.6.32 and .33), or can it wait until 2.6.34?
Should be fine for .34 only.
Thanks,
Kay
next prev parent reply other threads:[~2010-01-14 5:11 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 [this message]
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
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=ac3eb2511001132111t7ac93f97xe1e54d93e3a43b02@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=greg@kroah.com \
--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).