linux-kernel - Re: [PATCH 0/7] overlay filesystem v9

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110519180558.GJ3702@shadowen.org>
Date:	Thu, 19 May 2011 19:05:58 +0100
From:	Andy Whitcroft <apw@...onical.com>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	viro@...IV.linux.org.uk, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	nbd@...nwrt.org, neilb@...e.de, hramrach@...trum.cz,
	jordipujolp@...il.com
Subject: Re: [PATCH 0/7] overlay filesystem v9

On Thu, May 19, 2011 at 07:44:54PM +0200, Miklos Szeredi wrote:

> Forgot to attach the patch?

Yep, should be in your inbox now.

> >
> > With this in place I have been able to boot a Natty release live CD
> > image, and upgrade it in place to the latest and greatest of everything.
> > Very nice.  Thanks for your work continuing work on overlayfs.  It is
> > starting to look good enough to merge.
> >
> > Comments?
> 
> I'd be happier if the LSM module were fixed not to peek inside the inode
> structure.  Some filesystems (notably network ones) do not guarantee i_*
> to be up-to-date, relying on these is not a good idea.

I wonder what what the official way to get ownership information for an
inode is if we cannot rely on those.  I am happy to get the Yama LSM
fixed up if they are doing something wrong.

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