linux-kernel - Re: [PATCH 04/10] bcache: clean up hacks around bio_split

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: <CAF1ivSb5BwVZG844+ZbvWN+UW0WYq5hNOuhdXAQLQ0Ose6iinA@mail.gmail.com>
Date:	Tue, 28 Apr 2015 22:43:23 -0700
From:	Ming Lin <mlin@...nel.org>
To:	Christoph Hellwig <hch@....de>
Cc:	lkml <linux-kernel@...r.kernel.org>, Jens Axboe <axboe@...nel.dk>,
	Kent Overstreet <kent.overstreet@...il.com>,
	Dongsu Park <dongsu.park@...fitbricks.com>,
	linux-bcache@...r.kernel.org
Subject: Re: [PATCH 04/10] bcache: clean up hacks around bio_split_pool

On Tue, Apr 28, 2015 at 5:14 AM, Christoph Hellwig <hch@....de> wrote:
> On Mon, Apr 27, 2015 at 11:48:31PM -0700, Ming Lin wrote:
>> From: Kent Overstreet <kent.overstreet@...il.com>
>>
>> There has been workarounds only in bcache, for splitting pool as well
>> as submitting bios. Since generic_make_request() is able to handle
>> arbitrarily sized bios, it's now possible to delete those hacks.
>
> The Subject and description look confusing to me.
>
> From me reading of the code I'd word it as:
>
> Subject: bcache: remove driver private bio splitting code
>
> The bcache driver has always accepted arbitrarily large bios and split
> them internally.  Now that every driver must accept arbitrarily large
> bios this code isn't nessecary anymore.

Will update it.
--
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/