Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kbusch@kernel.org (Keith Busch)
Subject: PROBLEM: call trace triggered in 5.1.1 in drivers/nvme/host/pci.c, 5.0.11 ok
Date: Tue, 14 May 2019 08:23:37 -0600	[thread overview]
Message-ID: <20190514142337.GA19881@localhost.localdomain> (raw)
In-Reply-To: <20190514141439.GA14213@lst.de>

On Tue, May 14, 2019@04:14:39PM +0200, Christoph Hellwig wrote:
> On Tue, May 14, 2019@10:12:22PM +0800, Ming Lei wrote:
> > The two aren't merged because the default segment size(BLK_MAX_SEGMENT_SIZE) is 64KB,
> 
> Yep.
> 
> > and the following patch may fix this issue:
> 
> Or this one posted yesterday for that matter:
> 
> https://marc.info/?l=linux-block&m=155772952511144&w=2

Nice, either one looks good. We could also safely cap it to
(limits->max_hw_sectors << 9) instead of UINT_MAX.

  reply	other threads:[~2019-05-14 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAC=wYCGgPQPjUUjQTZh4H7b8WRQFGmbKCBRAq75g1BXjBR0L0Q@mail.gmail.com>
2019-05-14  5:20 ` PROBLEM: call trace triggered in 5.1.1 in drivers/nvme/host/pci.c, 5.0.11 ok Christoph Hellwig
     [not found]   ` <CAC=wYCFhKR5YrAwL1agz=USg3DAkx5BtXAfv64nOfTrwTji40Q@mail.gmail.com>
2019-05-14  5:58     ` Christoph Hellwig
     [not found]       ` <CAC=wYCECcfqoDDMcgVj-4dAEUxNpY62vAEMOD8-eGrZK8wOV-g@mail.gmail.com>
2019-05-14 13:54         ` Keith Busch
2019-05-14 14:12           ` Ming Lei
2019-05-14 14:14             ` Christoph Hellwig
2019-05-14 14:23               ` Keith Busch [this message]
     [not found]               ` <CAC=wYCFzdNNiaXWoAEMoj00f5enk3mJzQrUL9CjZD2RRRxAXNg@mail.gmail.com>
2019-05-14 22:22                 ` Keith Busch

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=20190514142337.GA19881@localhost.localdomain \
    --to=kbusch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox