From: hch@infradead.org (Christoph Hellwig)
Subject: crash in sg_alloc_table_chained
Date: Mon, 23 Jan 2017 23:47:56 -0800 [thread overview]
Message-ID: <20170124074756.GB27932@infradead.org> (raw)
In-Reply-To: <8C8F83F9-BDBB-4B59-BA4E-BAA34CB2E20D@cavium.com>
Hi Darren,
you probably want this patch that I sent last week:
"Subject: [PATCH] nvme-fc: use blk_rq_nr_phys_segments"
next prev parent reply other threads:[~2017-01-24 7:47 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
2017-01-23 23:10 ` Trapp, Darren
2017-01-24 7:47 ` Christoph Hellwig [this message]
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=20170124074756.GB27932@infradead.org \
--to=hch@infradead.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