[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1JtGfH-0008Bv-MI@pomaz-ex.szeredi.hu>
Date: Tue, 06 May 2008 08:28:39 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: gregkh@...e.de
CC: miklos@...redi.hu, akpm@...ux-foundation.org, hch@...radead.org,
viro@...IV.linux.org.uk, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: [patch 06/15] sysfs: dont call notify_change
> > sysfs_chmod_file() calls notify_change() to change the permission bits
> > on a sysfs file. Replace with explicit call to sysfs_setattr() and
> > fsnotify_change().
> >
> > This is equivalent, except that security_inode_setattr() is not
> > called. This function is called by drivers, so the security checks do
> > not make any sense.
>
> Are you sure? As a user, you can chmod the sysfs file and it will
> stick,
Right, but that's not sysfs_chmod_file() but sys_chmod(), which calls
notify_change(), which calls security_inode_setattr().
sysfs_chmod_file() is just called by a couple of drivers to change the
file mode during operation, it's never called by user action directly.
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists