All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Kalle Valo <kvalo@kernel.org>, Pei Xiao <xiaopei01@kylinos.cn>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"xiaopeitux@foxmail.com" <xiaopeitux@foxmail.com>,
	"xiongxin@kylinos.cn" <xiongxin@kylinos.cn>
Subject: RE: [PATCH] net: wireless: realtek/rtw89: Add check null return of kmalloc
Date: Wed, 30 Oct 2024 00:35:56 +0000	[thread overview]
Message-ID: <4f5eee8cb4024571a9a78af97aecab67@realtek.com> (raw)
In-Reply-To: <8734kf2o77.fsf@kernel.org>

Kalle Valo <kvalo@kernel.org> wrote:
> Pei Xiao <xiaopei01@kylinos.cn> writes:
> 
> > kmalloc may fail, return might be NULL and will cause
> > NULL pointer dereference later.
> >
> > Signed-off-by: Pei Xiao <xiaopei01@kylinos.cn>
> 
> We use 'wifi: rtw89:' in the title, please check the documentation below
> for more.
> 

A way to known subject prefix is to use git log with the files touched by
this patch:
   git log --oneline drivers/net/wireless/realtek/rtw89/coex.c

Also subject can point out specific function. Then my opinion is
  "wifi: rtw89: coex: check NULL return of kmalloc in btc_fw_set_monreg()"


  reply	other threads:[~2024-10-30  0:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29  9:12 [PATCH] net: wireless: realtek/rtw89: Add check null return of kmalloc Pei Xiao
2024-10-29 10:33 ` Kalle Valo
2024-10-30  0:35   ` Ping-Ke Shih [this message]
2024-10-30  3:12     ` Pei Xiao
2024-10-30  3:13       ` Pei Xiao
2024-10-29 20:37 ` Markus Elfring

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=4f5eee8cb4024571a9a78af97aecab67@realtek.com \
    --to=pkshih@realtek.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=xiaopei01@kylinos.cn \
    --cc=xiaopeitux@foxmail.com \
    --cc=xiongxin@kylinos.cn \
    /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.