From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Cc: drbd-user@linbit.com, Lars Marowsky-Bree <lmb@suse.de>, axboe@suse.de
Subject: Re: [Drbd-dev] [fix] drbd uses wrong API for struct bio
Date: Tue, 25 Jan 2005 10:26:11 +0100 [thread overview]
Message-ID: <200501251026.11669.philipp.reisner@linbit.com> (raw)
In-Reply-To: <20050124232318.GV5638@marowsky-bree.de>
Am Dienstag, 25. Januar 2005 00:23 schrieb Lars Marowsky-Bree:
> On 2005-01-23T17:16:33, Lars Marowsky-Bree <lmb@suse.de> wrote:
>
> The attached patch fixes drbds useage of bios up some. The proper fix
> would be to indeed change it over to use bio_alloc(), bio_get/put(),
> bio_add_page(), bio_clone (instead of __bio_clone) et cetera, but that
> fix is too complex for the timeframe I have right now.
>
> This should keep drbd-0.7.8 from oopsing not only on the SLES9 SP1
> kernel but also the recent 2.6.10-ac series.
>
> (I could possibly _code_ it, but it'd be too invasive and I'm weary of
> the side-effects it might have and the QA would take too long. There's a
> number of potential cleanups like further consolidation between
> drbd_prepare_req_write/_read and others, but I'd propose to do that for
> the drbd-0.8 branch instead when we can do away with 2.4.)
>
> Please comment on the patch, I'd be grateful.
>
Hi Lars,
the patch looks good so far. I am really happy that you have choosen
to go the less intrusive way for drbd-07.
Changing it over to alloc_bio() is something for drbd-08.
[...]
ONLY_IN_26(unsigned int ee_size;)
ONLY_IN_26(sector_t ee_sector;)
- // THINK: maybe we rather want bio_alloc(GFP_*,1)
+ // TODO: we rather want bio_alloc(GFP_*,1) all through the code!
ONLY_IN_26(struct bio_vec ee_bvec;)
I am wondering if with a private copy of the bio_vec if we already
have a copy of the IO operations size and start sector that is
still in place after the IO operation completed.
-> If this is the case we could drop the ee_size and ee_sector members
and take them form e.g. ee_bvec
Jens, I guess you can answer that question easily.
I will commit it to SVN...
-Philipp
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :
next prev parent reply other threads:[~2005-01-25 9:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 16:16 [Drbd-dev] drbd uses wrong API for struct bio Lars Marowsky-Bree
2005-01-24 8:24 ` [Drbd-dev] " Jens Axboe
2005-01-24 12:32 ` Helmut Wollmersdorfer
2005-01-24 12:35 ` Lars Marowsky-Bree
2005-01-24 9:10 ` Jens Axboe
2005-01-24 9:28 ` Lars Marowsky-Bree
2005-01-24 9:58 ` Lars Marowsky-Bree
2005-01-24 10:23 ` Jens Axboe
2005-01-24 10:28 ` Lars Marowsky-Bree
2005-01-24 12:24 ` Lars Marowsky-Bree
2005-01-24 12:52 ` Lars Marowsky-Bree
2005-01-24 14:29 ` Philipp Reisner
2005-01-26 11:15 ` Lars Ellenberg
2005-01-24 14:27 ` Philipp Reisner
2005-01-24 14:27 ` [Drbd-dev] " Philipp Reisner
2005-01-24 14:37 ` Lars Marowsky-Bree
2005-01-24 14:38 ` Philipp Reisner
2005-01-24 14:41 ` Lars Marowsky-Bree
2005-01-24 20:46 ` Lars Marowsky-Bree
2005-01-24 23:23 ` [Drbd-dev] [fix] " Lars Marowsky-Bree
2005-01-25 9:26 ` Philipp Reisner [this message]
2005-01-25 9:39 ` Jens Axboe
2005-01-25 9:58 ` Philipp Reisner
2005-01-25 10:05 ` Lars Marowsky-Bree
2005-01-25 11:44 ` Philipp Reisner
2005-01-25 9:53 ` Lars Marowsky-Bree
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200501251026.11669.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=axboe@suse.de \
--cc=drbd-dev@lists.linbit.com \
--cc=drbd-user@linbit.com \
--cc=lmb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox