From: Benjamin Block <bblock@linux.vnet.ibm.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
"#4 . 11+" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] bsg-lib: fix kernel panic resulting from missing allocation of reply-buffer
Date: Wed, 6 Sep 2017 16:15:09 +0200 [thread overview]
Message-ID: <20170906141509.GB8702@bblock-ThinkPad-W530> (raw)
In-Reply-To: <42e9ef4d-6981-2b0c-bdc3-afb5b1750666@kernel.dk>
On Wed, Sep 06, 2017 at 08:07:43AM -0600, Jens Axboe wrote:
> On 09/06/2017 07:44 AM, Christoph Hellwig wrote:
> > From: Benjamin Block <bblock@linux.vnet.ibm.com>
> >
> > Since we split the scsi_request out of struct request bsg fails to
> > provide a reply-buffer for the drivers. This was done via the pointer
> > for sense-data, that is not preallocated anymore.
>
> Confused, this is already in master, was included before 4.13 was
> finalized.
>
I think this is the backport for 4.11 and 4.12 as requested by Greg. I
just send a mail as answer that I would do it, but I guess Christoph
already had something in the pipe.
Or? I'll take a look.
Beste Gr��e / Best regards,
- Benjamin Block
--
Linux on z Systems Development / IBM Systems & Technology Group
IBM Deutschland Research & Development GmbH
Vorsitz. AufsR.: Martina Koederitz / Gesch�ftsf�hrung: Dirk Wittkopp
Sitz der Gesellschaft: B�blingen / Registergericht: AmtsG Stuttgart, HRB 243294
next prev parent reply other threads:[~2017-09-06 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 13:44 two small bsg fixes V2 Christoph Hellwig
2017-09-06 13:44 ` [PATCH 1/2] bsg-lib: fix kernel panic resulting from missing allocation of reply-buffer Christoph Hellwig
2017-09-06 14:07 ` Jens Axboe
2017-09-06 14:15 ` Benjamin Block [this message]
2017-09-06 14:18 ` Christoph Hellwig
2017-09-06 13:44 ` [PATCH 2/2] scsi_transport_fc: fix NULL pointer dereference in fc_bsg_job_timeout Christoph Hellwig
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=20170906141509.GB8702@bblock-ThinkPad-W530 \
--to=bblock@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox