From: Boaz Harrosh <bharrosh@panasas.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: jens.axboe@oracle.com, linux-scsi@vger.kernel.org,
James.Bottomley@HansenPartnership.com
Subject: Re: [PATCH] Revert "block: WARN in __blk_put_request() for potential bio leak"
Date: Wed, 10 Jun 2009 12:21:19 +0300 [thread overview]
Message-ID: <4A2F7B0F.1030205@panasas.com> (raw)
In-Reply-To: <20090610175238P.fujita.tomonori@lab.ntt.co.jp>
On 06/10/2009 11:52 AM, FUJITA Tomonori wrote:
> On Wed, 10 Jun 2009 11:45:14 +0300
> Boaz Harrosh <bharrosh@panasas.com> wrote:
>
>>>
>> The fact that ALL block drivers call it for proper service of ALL ULDS,
>> does it not make it a rule?
>
> BSG SMP code is not ULD.
>
BSG is certainly a ULD, Upper-Layer-Driver that can issue block commands
through block layer and block-queue.
SMP is a block device class that has it's own LLDs.
The way I understand
|---------| |--------------| |-----------|
| ULD |----->| block layer |----->| block LLD |
|---------| |--------------| |-----------|
So I meant block ULD or block layer user code. That is what I meant
by ULD, what do you mean?
<snip>
>
> FYI, you live in a land where very few live.
>
I thought I was working on the Linux-Kernel. Is there another
place I should be?
Boaz
next prev parent reply other threads:[~2009-06-10 9:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 10:44 [PATCH] Revert "block: WARN in __blk_put_request() for potential bio leak" FUJITA Tomonori
2009-06-09 11:53 ` Boaz Harrosh
2009-06-09 13:10 ` FUJITA Tomonori
2009-06-09 13:18 ` Jens Axboe
2009-06-09 13:32 ` Boaz Harrosh
2009-06-09 23:00 ` FUJITA Tomonori
2009-06-10 8:15 ` Boaz Harrosh
2009-06-10 8:29 ` FUJITA Tomonori
2009-06-10 8:34 ` Boaz Harrosh
2009-06-11 10:10 ` FUJITA Tomonori
2009-06-10 8:45 ` Boaz Harrosh
2009-06-10 8:52 ` FUJITA Tomonori
2009-06-10 9:21 ` Boaz Harrosh [this message]
2009-06-10 9:36 ` FUJITA Tomonori
2009-06-10 9:48 ` Boaz Harrosh
2009-06-10 10:01 ` FUJITA Tomonori
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=4A2F7B0F.1030205@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.