linux-kernel - Re: Block layer projects that I haven't had time for

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: <20141208114813.GA2724@gmail.com>
Date:	Mon, 8 Dec 2014 12:48:13 +0100
From:	Dongsu Park <dongsu.park@...fitbricks.com>
To:	Kent Overstreet <kmo@...erainc.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jens Axboe <axboe@...nel.dk>,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: Block layer projects that I haven't had time for

Thanks for the reply.

On 05.12.2014 19:02, Kent Overstreet wrote:
> On Thu, Dec 04, 2014 at 12:00:27PM +0100, Dongsu Park wrote:
> > Playing a little with your block_stuff tree based on 3.15, however,
> > I think there still seems to be a couple of issues.
> > First of all, it doesn't work with virtio-blk. A testing Qemu VM panics
> > at the very early stage of booting. This issue should be addressed as
> > the first step, so that other parts can be tested.
> 
> Really? I was testing with virtio-blk, that's odd..

The culprit seems to be the plugging commit.
Before that change, it works well also with virtio-blk.
Though that's not the only issue...

> > Moreover, I've already tried to rebase these patches on top of current
> > mainline, 3.18-rc7. It's now compilable, but it seems to introduce
> > more bugs about direct-IO. I didn't manage to find out the reason.
> > I'd need to also look at the previous review comments in [1], [2].
> > 
> > Don't you have other trees based on top of 3.17 or higher?
> > If not, can I create my own tree based on 3.18-rc7 to publish?
> 
> Yeah, I'd post what you have now and I'll try and take a look.

I've created a git tree to include what I have right now.
Please see <https://github.com/dongsupark/linux>.

To be able to handle different issues one by one,
I got the entire tree separated out into 4 branches based on 3.18.

* block-generic-req-for-next : the most stable branch you can test with.
  With this branch, you can test most of block drivers as well as file
  systems with less critical bugs. Though it's not 100% perfect yet,
  e.g. btrfs doesn't seem to work quite well. Thus more tests are needed.

* block-mpage-bvecs-for-next : block-generic-req-for-next + multipage bvecs.
  This branch shows a critical issue that writing blocks to ext4 rootfs
  causes the whole system to crash. Need-to-investigate.

* block-plug-for-next: block-mpage-bvecs-for-next + plugging.
  This branch has an additional bug with virtio-blk, that the kernel
  panics at the very early stage of booting. Need-to-investigate.

* block-dio-rewrite-for-next: block-plug-for-next + dio-rewriting.
  This branch has more issues w.r.t. direct-io. For example, dio_init()
  causes the kernel to panic at the early stage of booting.

All branches are compilable. But it's still somehow half-way complete.
Commit messages should be properly written too, so that they can be posted
to mailing lists.

Regards,
Dongsu
--
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/