From: keith.busch@intel.com (Keith Busch)
Subject: crash in sg_alloc_table_chained
Date: Mon, 23 Jan 2017 18:08:39 -0500 [thread overview]
Message-ID: <20170123230838.GB10771@localhost.localdomain> (raw)
In-Reply-To: <8C8F83F9-BDBB-4B59-BA4E-BAA34CB2E20D@cavium.com>
On Mon, Jan 23, 2017@10:53:04PM +0000, Trapp, Darren wrote:
> Gents,
>
> I am using 4.10rc4 kernel with the FC-NVME transport to format a partition on a remote nvme device. I?ve created a partition on the device, but when I try and create a FS via:
>
> Mkfs ?t ext3 /dev/nvme0n1p1
>
> I get a crash in sg_alloc_table_chained at the BUG_ON(!nents). It is called from nvme_fc_map_data:
> ret = sg_alloc_table_chained(&freq->sg_table, rq->nr_phys_segments,
> freq->sg_table.sgl);
>
> In this case, rq->nr_phys_segments is 0. For reference blk_rq_payload_bytes returned 0x10.
>
> Any ideas what is going on?
Just to confirm a suspicion, is it successful if you run:
# mkfs.ext3 /dev/nvme0n1p1 -E nodiscard
?
next prev parent reply other threads:[~2017-01-23 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 22:53 crash in sg_alloc_table_chained Trapp, Darren
2017-01-23 23:08 ` Keith Busch [this message]
2017-01-23 23:10 ` Trapp, Darren
2017-01-24 7:47 ` Christoph Hellwig
2017-01-24 19:20 ` Trapp, Darren
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=20170123230838.GB10771@localhost.localdomain \
--to=keith.busch@intel.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