From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Pan Bian <bianpan2016@163.com>
Cc: Satish Kharat <satishkh@cisco.com>,
Sesidhar Baddela <sebaddel@cisco.com>,
Karan Tilak Kumar <kartilak@cisco.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] scsi: fnic: fix use after free
Date: Tue, 05 Nov 2019 00:22:12 -0500 [thread overview]
Message-ID: <yq1a79a524b.fsf@oracle.com> (raw)
In-Reply-To: <1572881182-37664-1-git-send-email-bianpan2016@163.com> (Pan Bian's message of "Mon, 4 Nov 2019 23:26:22 +0800")
Pan,
> The memory chunk io_req is released by mempool_free. Accessing
> io_req->start_time will result in a use after free bug. The variable
> start_time is a backup of the timestamp. So, use start_time here to
> avoid use after free.
Applied to 5.5/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-11-05 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 15:26 [PATCH 1/1] scsi: fnic: fix use after free Pan Bian
2019-11-05 5:22 ` Martin K. Petersen [this message]
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=yq1a79a524b.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bianpan2016@163.com \
--cc=jejb@linux.ibm.com \
--cc=kartilak@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.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