From: Mike Christie <michael.christie@oracle.com>
To: Gulam Mohamed <gulam.mohamed@oracle.com>,
John Garry <john.g.garry@oracle.com>,
Martin Petersen <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>
Subject: Re: [PATCH 6.19/scsi-queue] scsi: target: core: Add emulation for REPORT_IDENTIFICATION_INFORMATION
Date: Tue, 25 Nov 2025 12:01:56 -0600 [thread overview]
Message-ID: <ba7e29ab-6900-4ca9-ab38-ca459442a6f3@oracle.com> (raw)
In-Reply-To: <IA1PR10MB7240FA764470DDBC324840E898D7A@IA1PR10MB7240.namprd10.prod.outlook.com>
On 11/19/25 1:58 PM, Gulam Mohamed wrote:
>>> + buf = kzalloc(buf_len, GFP_KERNEL);
>>> + if (!buf) {
>>> + pr_err("Unable to allocate response buffer for IDENTITY
>> INFO\n");
>>> + return TCM_LOGICAL_UNIT_COMMUNICATION_FAILURE;
>>> + }
>>> +
>>> + scnprintf(&buf[header_len], buf_len - header_len, "%s",
>>> + dev->t10_wwn.pd_text_id_info);
>>> +
>>> + put_unaligned_be16(id_len, &buf[2]);
>>> +
>>> + rbuf = (cmd);
>>
>> is it really ok if this returns NULL?
> I think its ok to return NULL. We just don't send any information. I kept it like this because I don't see any information defined by protocol when the memory mapping fails.
> Mike, Can you please correct me if I am missing anything?
It's probably best to return a failure so the caller knows that
we might have a ID but we can't return it. It will also match the
case above when we can't allocate memory.
next prev parent reply other threads:[~2025-11-25 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 19:13 [PATCH 6.19/scsi-queue] scsi: target: core: Add emulation for REPORT_IDENTIFICATION_INFORMATION Gulam Mohamed
2025-11-17 16:19 ` John Garry
2025-11-19 19:58 ` Gulam Mohamed
2025-11-25 18:01 ` Mike Christie [this message]
2025-11-26 11:53 ` John Garry
2025-11-27 9:27 ` Gulam Mohamed
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=ba7e29ab-6900-4ca9-ab38-ca459442a6f3@oracle.com \
--to=michael.christie@oracle.com \
--cc=gulam.mohamed@oracle.com \
--cc=john.g.garry@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=target-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox