From: Ming Lei <ming.lei@redhat.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Bart Van Assche <bart.vanassche@wdc.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
Hannes Reinecke <hare@suse.com>,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH 1/2] scsi-mq: Only show the CDB if available
Date: Tue, 5 Dec 2017 12:00:16 +0800 [thread overview]
Message-ID: <20171205040015.GA9885@ming.t460p> (raw)
In-Reply-To: <yq1zi6x3knv.fsf@oracle.com>
On Mon, Dec 04, 2017 at 10:42:28PM -0500, Martin K. Petersen wrote:
>
> Hi Ming,
>
> > Please cook a patch for fixing the crash issue only, since we need
> > to backport the fix to stable kernel.
>
> I thought you were going to submit a V5 that addressed James' concerns?
>
> --
> Martin K. Petersen Oracle Linux Engineering
Hi Martin,
I replied in the following link for James's concerns:
https://marc.info/?l=linux-block&m=151074751321108&w=2
The fact is that use-after-free can't avoided at all, no matter if
we set the cmnd to NULL before calling free, that means we have to
handle use-after-free well in scsi_show_rq(), so we don't need to
touch the free code.
So V4 is well enough for merge, IMO.
Thanks,
Ming
next prev parent reply other threads:[~2017-12-05 4:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 0:38 [PATCH 0/2] Show commands stuck in a timeout handler in debugfs Bart Van Assche
2017-12-05 0:38 ` [PATCH 1/2] scsi-mq: Only show the CDB if available Bart Van Assche
2017-12-05 1:15 ` Ming Lei
2017-12-05 1:59 ` Bart Van Assche
2017-12-05 5:00 ` Ming Lei
2017-12-05 16:22 ` Bart Van Assche
2017-12-05 16:38 ` Ming Lei
2017-12-05 16:43 ` James Bottomley
2017-12-06 1:16 ` Ming Lei
2017-12-05 17:51 ` Bart Van Assche
2017-12-05 3:42 ` Martin K. Petersen
2017-12-05 4:00 ` Ming Lei [this message]
2017-12-05 0:38 ` [PATCH 2/2] blk-mq-debugfs: Also show requests that have not yet been started Bart Van Assche
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=20171205040015.GA9885@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).