From: David Zeuthen <david@fubar.dk>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev change event
Date: Thu, 10 Jul 2008 14:21:20 +0000 [thread overview]
Message-ID: <1215699680.6152.7.camel@x61.fubar.dk> (raw)
In-Reply-To: <486CBF8C.1090406@redhat.com>
On Thu, 2008-07-03 at 23:50 +0200, Kay Sievers wrote:
> On Thu, Jul 3, 2008 at 21:48, Bill Nottingham <notting@redhat.com> wrote:
> > Marco d'Itri (md@Linux.IT) said:
> >> On Jul 03, Harald Hoyer <harald@redhat.com> wrote:
> >>
> >> > With recent changes, udev processes "change" events for removable devices
> >> > and resets the permissions, if it has changed since creation. Is this
> >> > intended? Or do we just want a new vol_id symlink?
> >> I think this is intended: manually changing the permissions of dynamic
> >> devices is not supposed to work.
> >
> > ....? How do you handle ACLs for local users, then?
>
> Re-apply them, with the same logic that did it in the first place?
Racy. The ACL's are applied long after udev stopped processing rules.
Better to fix udev to only apply permissions on "add" events.
David
next prev parent reply other threads:[~2008-07-10 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 12:01 udev change event Harald Hoyer
2008-07-03 12:16 ` Marco d'Itri
2008-07-03 19:48 ` Bill Nottingham
2008-07-03 21:50 ` Kay Sievers
2008-07-03 21:57 ` Marco d'Itri
2008-07-04 9:47 ` Harald Hoyer
2008-07-07 14:55 ` Bill Nottingham
2008-07-07 15:05 ` Marco d'Itri
2008-07-07 15:25 ` Bill Nottingham
2008-07-07 15:28 ` Marco d'Itri
2008-07-07 15:34 ` Bill Nottingham
2008-07-10 14:21 ` David Zeuthen [this message]
2008-07-10 18:44 ` Kay Sievers
2008-07-10 23:00 ` Kay Sievers
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=1215699680.6152.7.camel@x61.fubar.dk \
--to=david@fubar.dk \
--cc=linux-hotplug@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).