From: Jens Axboe <axboe@suse.de>
To: Sean Estabrooks <seanlkml@rogers.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Block layer bug handling partial bvec
Date: Sun, 27 Jul 2003 14:47:50 +0200 [thread overview]
Message-ID: <20030727124750.GB2261@suse.de> (raw)
In-Reply-To: <099001c35434$f9ac3130$7f0a0a0a@lappy7>
On Sun, Jul 27 2003, Sean Estabrooks wrote:
> Previously I submitted a patch for "blk: request botched" on floppy
> write. While the patch did make the floppy work, Jens mentioned
> that an underlying error still existed. This spurred me on to look a
> little deeper and finally i found the root cause.
>
> There is a bug in "ll_rw_blk.c" handling partial bvec submissions.
> For whatever reason the floppy driver was triggering it more than
> other users. Note that with the attached patch, my previous
> floppy_ patch is no longer needed.
Good catch! Applied.
--
Jens Axboe
prev parent reply other threads:[~2003-07-27 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 11:48 [PATCH] Block layer bug handling partial bvec Sean Estabrooks
2003-07-27 12:47 ` Jens Axboe [this message]
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=20030727124750.GB2261@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanlkml@rogers.com \
/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;
as well as URLs for NNTP newsgroup(s).