linux-kernel - Re: [RFC PATCH 26/26] UBIFS: include FS to compilation

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: <20080426093732.GB17730@infradead.org>
Date:	Sat, 26 Apr 2008 05:37:32 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	Artem.Bityutskiy@...ia.com, Artem Bityutskiy <dedekind@...dex.ru>,
	LKML <linux-kernel@...r.kernel.org>,
	Adrian Hunter <ext-adrian.hunter@...ia.com>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: [RFC PATCH 26/26] UBIFS: include FS to compilation

On Tue, Apr 01, 2008 at 02:33:37PM +0300, Pekka Enberg wrote:
> I don't know how many times I have to say this: you're doing it at the
> wrong level! The reason you want to compile them out is because you've
> added crap like this all over your code paths:
> 
>         ubifs_assert(PageLocked(page));
>         ubifs_assert(!PageChecked(page));
>         ubifs_assert(!PagePrivate(page));
> 
> So instead of arguing about this you really ought to look at what
> SLUB, for example, does. It's perfectly okay to have _debugging
> checks_ compiled out (stuff like verify_inode and such) but at the
> assertion level it makes no sense whatsoever!

Yes, having this in filesystems is not very nice.  If someone feels
very strong about interface assertation we should add them at the
method level boundary so that the interface is verified for all
filesystems.

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