linux-kernel - Re: time to move fs/bio.c to block/ ?

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: <20140519142519.GI18016@ZenIV.linux.org.uk>
Date:	Mon, 19 May 2014 15:25:19 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	Christoph Hellwig <hch@...radead.org>, linux-kernel@...r.kernel.org
Subject: Re: time to move fs/bio.c to block/ ?

On Mon, May 19, 2014 at 08:14:36AM -0600, Jens Axboe wrote:
> On 05/19/2014 08:13 AM, Christoph Hellwig wrote:
> > I recently saw patches to fs/bio.c that were sent to Al instead of Jens.
> > I think having bio.c in fs/ is rather confusing, so maybe it's time to
> > include the simple git-mv for it in the your for-next tree?
> 
> Sure, I've been thinking that too for a while. I'll do the move.

While you are at it, could you take bio-integrity.c with it?  _That_
has zero excuse being anywhere in fs/* - not even "filesystem code
uses quite a few functions from that sucker" as with bio.c.
FWIW, consider the move ACKed.
--
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/