From: michael.christie@oracle.com
To: Yang Li <yang.lee@linux.alibaba.com>,
martin.petersen@oracle.com,
Dmitry Bogdanov <d.bogdanov@yadro.com>
Cc: linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] scsi: target: iscsi: Fix NULL pointer dereference in iscsi_conn_auth_required()
Date: Mon, 13 Jun 2022 10:11:17 -0500 [thread overview]
Message-ID: <390b38f7-462a-bfad-5e46-21b4e72f8a39@oracle.com> (raw)
In-Reply-To: <20220613014321.107045-1-yang.lee@linux.alibaba.com>
On 6/12/22 8:43 PM, Yang Li wrote:
> Fix following coccicheck error:
> ./drivers/target/iscsi/iscsi_target_nego.c:831:13-26: ERROR: se_nacl is
> NULL but dereferenced.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
This was just added in Martin's 5.20 tree in:
a75fcb0912a549c6c1da8395f33271ce06e84acd
scsi: target: iscsi: Extract auth functions
Do we need a Fixes or should the original patch be fixed?
Patch looks ok to me, so if we just add it:
Reviewed-by: Mike Christie <michael.christie@oracle.com>
> ---
> drivers/target/iscsi/iscsi_target_nego.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/target/iscsi/iscsi_target_nego.c b/drivers/target/iscsi/iscsi_target_nego.c
> index 9ce35a59962b..fb93a1173954 100644
> --- a/drivers/target/iscsi/iscsi_target_nego.c
> +++ b/drivers/target/iscsi/iscsi_target_nego.c
> @@ -827,8 +827,7 @@ static bool iscsi_conn_auth_required(struct iscsit_conn *conn)
> */
> se_nacl = conn->sess->se_sess->se_node_acl;
> if (!se_nacl) {
> - pr_debug("Unknown ACL %s is trying to connect\n",
> - se_nacl->initiatorname);
> + pr_debug("Unknown ACL is trying to connect\n");
> return true;
> }
>
next prev parent reply other threads:[~2022-06-13 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 1:43 Yang Li
2022-06-13 15:11 ` michael.christie [this message]
2022-06-14 2:07 ` Martin K. Petersen
2022-06-17 2:21 ` 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=390b38f7-462a-bfad-5e46-21b4e72f8a39@oracle.com \
--to=michael.christie@oracle.com \
--cc=abaci@linux.alibaba.com \
--cc=d.bogdanov@yadro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=target-devel@vger.kernel.org \
--cc=yang.lee@linux.alibaba.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
all inboxes | Powered by JetHome®