From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Garry <john.garry@huawei.com>
Cc: <jinpu.wang@cloud.ionos.com>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <damien.lemoal@opensource.wdc.com>,
<Ajish.Koshy@microchip.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <Viswas.G@microchip.com>,
<chenxiang66@hisilicon.com>
Subject: Re: [PATCH 0/3] scsi: pm8001: Documentation and use-after-free fixes
Date: Mon, 31 Jan 2022 16:40:30 -0500 [thread overview]
Message-ID: <yq11r0na8jg.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1643289172-165636-1-git-send-email-john.garry@huawei.com> (John Garry's message of "Thu, 27 Jan 2022 21:12:49 +0800")
John,
> A few fixes:
> - Remedy make W=1 warning for undescribed param
> - 2x use-after-free fixes for these KASAN warnings:
Applied to 5.17/scsi-fixes, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-01-31 21:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 13:12 [PATCH 0/3] scsi: pm8001: Documentation and use-after-free fixes John Garry
2022-01-27 13:12 ` [PATCH 1/3] scsi: pm8001: Fix warning for undescribed param in process_one_iomb() John Garry
2022-01-27 23:06 ` Damien Le Moal
2022-01-28 6:17 ` Jinpu Wang
2022-01-27 13:12 ` [PATCH 2/3] scsi: pm8001: Fix use-after-free for aborted TMF sas_task John Garry
2022-01-27 23:07 ` Damien Le Moal
2022-01-28 6:18 ` Jinpu Wang
2022-01-27 13:12 ` [PATCH 3/3] scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task John Garry
2022-01-27 23:08 ` Damien Le Moal
2022-01-28 6:18 ` Jinpu Wang
2022-01-31 21:40 ` Martin K. Petersen [this message]
2022-02-01 2:03 ` [PATCH 0/3] scsi: pm8001: Documentation and use-after-free fixes Martin K. Petersen
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=yq11r0na8jg.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=Ajish.Koshy@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=chenxiang66@hisilicon.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jejb@linux.ibm.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.