From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: <kartilak@cisco.com>, <sebaddel@cisco.com>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <hare@suse.de>,
<JBottomley@Odin.com>, <nmusini@cisco.com>,
<linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi: snic: Fix possible UAF in snic_tgt_create
Date: Fri, 25 Nov 2022 19:31:18 -0500 [thread overview]
Message-ID: <yq1fse6pne8.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20221117035100.2944812-1-cuigaosheng1@huawei.com> (Gaosheng Cui's message of "Thu, 17 Nov 2022 11:51:00 +0800")
Gaosheng,
> Smatch report warning as follows:
>
> drivers/scsi/snic/snic_disc.c:307 snic_tgt_create() warn:
> '&tgt->list' not removed from list
Applied to 6.2/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-11-26 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 3:51 [PATCH] scsi: snic: Fix possible UAF in snic_tgt_create Gaosheng Cui
2022-11-26 0:31 ` Martin K. Petersen [this message]
2022-12-01 3:45 ` 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=yq1fse6pne8.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=JBottomley@Odin.com \
--cc=cuigaosheng1@huawei.com \
--cc=hare@suse.de \
--cc=jejb@linux.ibm.com \
--cc=kartilak@cisco.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nmusini@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