All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Govindan, Thiru" <GovinT@LOUISVILLE.STORTEK.COM>
Cc: "'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: FW:  Re. Allocation of scatter gather table in __init_io
Date: Mon, 9 Aug 2004 10:36:26 +0200	[thread overview]
Message-ID: <20040809083625.GP10418@suse.de> (raw)
In-Reply-To: <E5A17223DA27AB4DABB18A5955F4235545CFCE@EXCHVS1.louisville.stortek.com>

On Mon, Aug 09 2004, Govindan, Thiru wrote:
> Hi,
>     I'm running into an issue that seems to be caused by __init_io()
>     in scsi_merge.c. Apparently __init_io() is allocating the scatter
>     gather list before even merging the segments in the queue. In my
>     case the request nr_segments  has a value of 2 and the scatter
>     gather table is allocated for 2 entries. But  then the logic
>     merges the 2 segments into 1 and fills in one entry, my HBA driver
>     complains that one entry is invalid and panics. Can you clarify
>     how this works, I suppose getting mergeable segments in a request
>     is common and hence __init_io() must allocate the table after
>     having at least identified how may segments are really there. 
> 
> Is this a known issue and is there a patch that fixes this?

It has to allocate the space for the table to hold all items, so it's
expected. Sounds like you are not using the correct return value to
check what segment count you should pass the hardware.

-- 
Jens Axboe


  reply	other threads:[~2004-08-09  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09  4:50 FW: Re. Allocation of scatter gather table in __init_io Govindan, Thiru
2004-08-09  8:36 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-09  9:09 Govindan, Thiru
2004-08-09  9:14 ` Jens Axboe

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=20040809083625.GP10418@suse.de \
    --to=axboe@suse.de \
    --cc=GovinT@LOUISVILLE.STORTEK.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.