linux-kernel - Re: [git pull] vfs for rc2, part 1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100818165235.GA24783@infradead.org>
Date:	Wed, 18 Aug 2010 12:52:35 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Al Viro <viro@...iv.linux.org.uk>, Jan Kara <jack@...e.cz>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [git pull] vfs for rc2, part 1

On Wed, Aug 18, 2010 at 09:44:34AM -0700, Linus Torvalds wrote:
> On Wed, Aug 18, 2010 at 8:35 AM, Al Viro <viro@...iv.linux.org.uk> wrote:
> >
> > Jan Kara (1):
> > ? ? ?vfs: update ctime when changing the file's permission by setfacl
> 
> What dirties the inode for this case? It seems to just set i_ctime
> directly, how does it actually get written back to disk?
> 
> Or is this purely a tmpfs/shmfs issue? Maybe a comment on that would
> have been good.

Yes, that code currently is just used for in-memory filesystems. Both
the generic_acl name for the file and the vfs: prefix for the patch
are rather confusing.

--
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/