linux-kernel - Re: [PATCH 01/24] Unionfs: Documentation

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: <200701091716.l09HGO4l008783@agora.fsl.cs.sunysb.edu>
Date:	Tue, 9 Jan 2007 12:16:24 -0500
From:	Erez Zadok <ezk@...sunysb.edu>
To:	Trond Myklebust <trond.myklebust@....uio.no>
Cc:	Shaya Potter <spotter@...columbia.edu>, Jan Kara <jack@...e.cz>,
	Josef Sipek <jsipek@....cs.sunysb.edu>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, hch@...radead.org,
	viro@....linux.org.uk, torvalds@...l.org, mhalcrow@...ibm.com,
	David Quigley <dquigley@...sunysb.edu>,
	Erez Zadok <ezk@...sunysb.edu>
Subject: Re: [PATCH 01/24] Unionfs: Documentation 

In message <1168362231.6054.38.camel@...e.trondhjem.org>, Trond Myklebust writes:

> I'm saying that at the very least it should not Oops in these
> situations. As to whether or not they are something you want to handle
> more gracefully, that is up to you, but Oopses are definitely a
> showstopper.
> 
> Trond

I totally agree: oopsing is unacceptable.  Instead Unionfs should handle it
more gracefully than an oops.

Now, a lot of this "scare" in the past couple of days had been the result of
our documentation, which was intended to prevent people from mucking with
the lower f/s.  As Jeff said already yesterday, many of the possible oopses
were already fixed, and you'll be hard pressed right now to be able to
tickle more oopses.  But, to be sure, we'll run more tests, and fix whatever
else we can.

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