linux-kernel - Re: [PATCH 0/7] OMFS filesystem version 3

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]

Date:	Tue, 15 Apr 2008 13:11:20 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	hch@...radead.org, alan@...rguk.ukuu.org.uk, dwmw2@...radead.org,
	miklos@...redi.hu, me@...copeland.com,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 0/7] OMFS filesystem version 3

On Tue, 15 Apr 2008 22:24:32 +0300
Adrian Bunk <bunk@...nel.org> wrote:

> > Look, I have repeatedly described the reason why it is probable a poor
> > tradeoff to merge code such as this.  The only response has been "well
> > we've done it before", which is largely a non-reason.
> >...
> 
> It seems you missed the first point in my email:
> 
> We do not have a stable API for external modules, and part of the deal 
> is that external modules have the chance of entering the kernel where 
> they will get API changes automatically.
> 
> 
> Plus my other point that one might argue that OMFS adds support for some 
> hardware in which case a recent commandment by Linus would require it 
> has to be merged...

That's lawyerly trickery, sorry.  Take some set of guidelines and then say
"you are thereby committed to doing X".

We're not committed to doing anything and it would be bad if we were. 
Let's apply common sense and judgement to each case on its own.

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