From: Juergen Gross <jgross@suse.com>
To: Kunwu Chan <chentao@kylinos.cn>,
boris.ostrovsky@oracle.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>,
Markus Elfring <Markus.Elfring@web.de>
Subject: Re: [PATCH v3] x86/xen: Add some null pointer checking to smp.c
Date: Mon, 12 Feb 2024 18:07:39 +0100 [thread overview]
Message-ID: <0d65f145-e086-44e5-9ae7-8acb3c3b05e2@suse.com> (raw)
In-Reply-To: <20240119094948.275390-1-chentao@kylinos.cn>
[-- Attachment #1.1.1: Type: text/plain, Size: 521 bytes --]
On 19.01.24 10:49, Kunwu Chan wrote:
> kasprintf() returns a pointer to dynamically allocated memory
> which can be NULL upon failure. Ensure the allocation was successful
> by checking the pointer validity.
>
> Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202401161119.iof6BQsf-lkp@intel.com/
> Suggested-by: Markus Elfring <Markus.Elfring@web.de>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2024-02-12 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 9:49 Kunwu Chan
2024-01-19 10:40 ` Markus Elfring
2024-01-22 7:47 ` Kunwu Chan
2024-01-20 14:45 ` Markus Elfring
2024-01-22 7:43 ` Kunwu Chan
2024-01-22 9:50 ` [v3] " Markus Elfring
2024-02-12 17:07 ` Juergen Gross [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=0d65f145-e086-44e5-9ae7-8acb3c3b05e2@suse.com \
--to=jgross@suse.com \
--cc=Markus.Elfring@web.de \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=chentao@kylinos.cn \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®