linux-kernel - [PATCH 000 of 4] Change prototype for bi_end

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-next>] [day] [month] [year] [list]

Message-ID: <20070927171111.3251.patches@notabene>
Date:	Thu, 27 Sep 2007 17:20:01 +1000
From:	NeilBrown <neilb@...e.de>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH 000 of 4] Change prototype for bi_end_io

Hi Jens,
 here are a few more patches from my set that makes various changes to bio
 submission and handling.

 These change the ->bi_end_io prototype so that
   1/ no 'size' is passed
   2/ there is no return value.

 The 'size' is not really of interest to any bi_end_io handler in existance. 
 It is really only an internal detail to the "request" handling in ll_rw_blk
 and lower levels.
 The return value is completely unused.

 After these patches, ->bi_end_io is only ever called once per bio.

 Note that the last patch makes lots and lots of simple changes.  I
 think I have found all the right places, but any recently added
 device drivers might still be using the old bi_end_io prototype.
 I'll grep again after these patches are in your tree.

 That patches are against linux-block as of an hour ago.

Thanks,
NeilBrown

Net result of the 4 patches:

 46 files changed, 166 insertions(+), 385 deletions(-)

 [PATCH 001 of 4] Remove flush_dry_bio_endio
 [PATCH 002 of 4] Only call bi_end_io once for any bio.
 [PATCH 003 of 4] Don't decrement bi_size in bio_endio.
 [PATCH 004 of 4] Drop 'size' argument from bio_endio and bi_end_io.
-
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/