public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Minu Jin <s9430939@naver.com>
Cc: gregkh@linuxfoundation.org, dan.carpenter@linaro.org,
	trohan2000@gmail.com, andy@kernel.org,
	linux-staging@lists.linux.dev, straube.linux@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/4] staging: rtl8723bs: replace rtw_malloc() with kmalloc()
Date: Tue, 3 Feb 2026 16:52:14 +0200	[thread overview]
Message-ID: <aYILnssCFT8ZPIvp@smile.fi.intel.com> (raw)
In-Reply-To: <20260131193001.303307-2-s9430939@naver.com>

On Sun, Feb 01, 2026 at 04:29:58AM +0900, Minu Jin wrote:
> Remove wrapper function _rtw_malloc() and macro rtw_malloc().
> Replace all rtw_malloc with kmalloc.

rtw_malloc()
kmalloc()

> All call sites are reviewed to select GFP_KERNEL or GFP_ATOMIC.
> 
> 1. GFP_KERNEL:
>    Used in paths that are executed in process context and are allowed to sleep.
> 
>    - Driver initialization and probe paths.
>    - Workqueue callbacks and cfg80211 configuration callbacks.
> 
> 2. GFP_ATOMIC:
>     Used in paths that must not sleep because they operate in atomic contexts.
> 
>    - Interrupt handlers and SoftIRQ contexts.
>    - Functions called while holding spinlocks.
>    - Low-level I/O operations (SDIO) (eg, sdio_read32())

> Replace kmalloc()/memcpy() with kmemdup() where possible.

This one probably better to have in a separate change (obviously before
this one).

> Replace sizeof(struct val) with sizeof(*ptr).
> Remove blank line after kmalloc().

...

> -	if (remainder_ielen > 0) {
> -		pbackup_remainder_ie = rtw_malloc(remainder_ielen);
> -		if (pbackup_remainder_ie && premainder_ie)
> -			memcpy(pbackup_remainder_ie, premainder_ie, remainder_ielen);
> +	if (remainder_ielen > 0 && premainder_ie) {
> +		pbackup_remainder_ie = kmemdup(premainder_ie, remainder_ielen, GFP_ATOMIC);
>  	}

No {} and it will be better to check pointer followed up with length check:

	if (premainder_ie && remainder_ielen)
		pbackup_remainder_ie = kmemdup(premainder_ie, remainder_ielen, GFP_ATOMIC);


...

> -	if (remainder_ielen > 0) {
> -		pbackup_remainder_ie = rtw_malloc(remainder_ielen);
> -		if (pbackup_remainder_ie)
> -			memcpy(pbackup_remainder_ie, premainder_ie, remainder_ielen);
> +	if (remainder_ielen > 0 && premainder_ie) {
> +		pbackup_remainder_ie = kmemdup(premainder_ie, remainder_ielen, GFP_ATOMIC);
>  	}

Ditto.

...

So, the above two should go before this patch.

...

> -		tmpbuf = rtw_malloc(n);
> +		tmpbuf = kmalloc(n, GFP_ATOMIC);
>  		if (!tmpbuf)
>  			return -1;

Side note, these '-1':s probably should be converted to '-ENOMEM':s.

...

> -			pmlmepriv->wps_probe_req_ie = rtw_malloc(wps_ielen);
> +			pmlmepriv->wps_probe_req_ie = kmemdup(wps_ie, wps_ielen, GFP_KERNEL);
>  			if (!pmlmepriv->wps_probe_req_ie)
>  				return -EINVAL;
>  
> -			memcpy(pmlmepriv->wps_probe_req_ie, wps_ie, wps_ielen);
>  			pmlmepriv->wps_probe_req_ie_len = wps_ielen;
>  		}

Move this to the 'kmemdup()' conversion patch (as mentioned above).


...

>  void *_rtw_zmalloc(u32 sz)
>  {
> -	void *pbuf = _rtw_malloc(sz);
> -
> +	void *pbuf = kmalloc(sz, in_interrupt() ? GFP_ATOMIC : GFP_KERNEL);

No, this has to be

	void *pbuf;

	pbuf = kmalloc(sz, in_interrupt() ? GFP_ATOMIC : GFP_KERNEL);

>  	if (pbuf)
>  		memset(pbuf, 0, sz);

So, why this simply can't be moved to kzalloc()?

...

>  	/* duplicate src */
> -	dup = rtw_malloc(src_len);
> +	dup = kmalloc(src_len, GFP_ATOMIC);
>  	if (dup) {
>  		dup_len = src_len;
>  		memcpy(dup, src, dup_len);

Obviously this is candidate for kmemdup().

...

>  	struct rtw_cbuf *cbuf;
>  
> -	cbuf = rtw_malloc(struct_size(cbuf, bufs, size));
> -
> +	cbuf = kmalloc(struct_size(cbuf, bufs, size), GFP_ATOMIC);
>  	if (cbuf) {

>  		cbuf->write = 0;
>  		cbuf->read = 0;

Maybe you want kzalloc() to begin with?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-02-03 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-31 19:29 [PATCH v4 0/4] remove memory allocation wrappers Minu Jin
2026-01-31 19:29 ` [PATCH v4 1/4] staging: rtl8723bs: replace rtw_malloc() with kmalloc() Minu Jin
2026-02-03 14:52   ` Andy Shevchenko [this message]
2026-01-31 19:29 ` [PATCH v4 2/4] staging: rtl8723bs: replace rtw_zmalloc() with kzalloc() Minu Jin
2026-02-03 15:11   ` Andy Shevchenko
2026-01-31 19:30 ` [PATCH v4 3/4] staging: rtl8723bs: replace skb allocation, copy wrappers Minu Jin
2026-02-03 15:13   ` Andy Shevchenko
2026-01-31 19:30 ` [PATCH v4 4/4] staging: rtl8723bs: remove unused allocation wrapper functions Minu Jin
2026-02-03 15:14   ` Andy Shevchenko

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=aYILnssCFT8ZPIvp@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=s9430939@naver.com \
    --cc=straube.linux@gmail.com \
    --cc=trohan2000@gmail.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