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: <20140519143337.GB568@infradead.org>
Date:	Mon, 19 May 2014 07:33:37 -0700
From:	Christoph Hellwig <hch@...radead.org>
To:	Jianyu Zhan <nasa4836@...il.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Jens Axboe <axboe@...nel.dk>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: time to move fs/bio.c to block/ ?

On Mon, May 19, 2014 at 10:28:16PM +0800, Jianyu Zhan wrote:
> Hi, Christoph, Jens,
> 
> BTW, just out of curiosity,  the VFS infrastructure code is just scatterd
> around the fs directory, which is quite suprised to a new comer that why
> there is "no" vfs stuff in fs directory.  Does it make sense to also collect
> them into a dedicated sub-dir, maybe vfs.  IMHO, this could make code
> skeleton more clear and could avoid such mis-sending patches in a long
> term maintainability view.

fs/*.[ch] shouldn't be much that isn't VFS in the broader sense
(including library functions). Besides the block files the only the only
things that might make sense to move out are binfmt*.c, signalfd.c
and timerfd.c (to kernel/ ?).

> 
> Thanks,
> Jianyu Zhan
---end quoted text---
--
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/