All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: Re: [PATCH 0/2] nvmet: consider req->sg_cnt for inline bio
Date: Tue, 4 May 2021 10:56:13 +0200	[thread overview]
Message-ID: <20210504085613.GA21953@lst.de> (raw)
In-Reply-To: <20210429184357.9185-1-chaitanya.kulkarni@wdc.com>

On Thu, Apr 29, 2021 at 11:43:55AM -0700, Chaitanya Kulkarni wrote:
> Hi,
> 
> While testing I came across the scenario where checking for the
> transfer size is not enough for inline bios, this issue is not easily
> reproducible with the test tools that I have.
> 
> This small patch-series adds an additional check so that we make sure 
> transfer size and the req->sg_cnt both fit in the inline bio for
> bdev and passthru backend.

How do you get the fragmented scatterlist?  Oh I guess this is due to
nvme-loop not using our page allocator but pages that come the
block layer?

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  parent reply	other threads:[~2021-05-04  8:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 18:43 [PATCH 0/2] nvmet: consider req->sg_cnt for inline bio Chaitanya Kulkarni
2021-04-29 18:43 ` [PATCH 1/2] nvmet: check sg_cnt for inline bio for bdev-ns Chaitanya Kulkarni
2021-05-04 20:00   ` Sagi Grimberg
2021-05-04 22:03   ` Chaitanya Kulkarni
2021-05-05  5:06     ` hch
2021-04-29 18:43 ` [PATCH 2/2] nvmet: check sg_cnt for inline bio for passthru Chaitanya Kulkarni
2021-05-04 20:00   ` Sagi Grimberg
2021-05-04  8:56 ` Christoph Hellwig [this message]
2021-05-04 21:16   ` [PATCH 0/2] nvmet: consider req->sg_cnt for inline bio Chaitanya Kulkarni
2021-05-05  4:57     ` Christoph Hellwig
2021-05-04 20:01 ` Sagi Grimberg

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=20210504085613.GA21953@lst.de \
    --to=hch@lst.de \
    --cc=chaitanya.kulkarni@wdc.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.