The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "dongchenchen (A)" <dongchenchen2@huawei.com>
To: Yunsheng Lin <linyunsheng@huawei.com>, <hawk@kernel.org>,
	<ilias.apalodimas@linaro.org>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<horms@kernel.org>, <almasrymina@google.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<zhangchangzhong@huawei.com>,
	<syzbot+204a4382fcb3311f3858@syzkaller.appspotmail.com>
Subject: Re: [PATCH net] page_pool: Fix use-after-free in page_pool_recycle_in_ring
Date: Mon, 26 May 2025 22:27:10 +0800	[thread overview]
Message-ID: <2c4a2655-2e0d-4c16-82e6-2d9d33d5a276@huawei.com> (raw)
In-Reply-To: <a5cc7765-0de2-47ca-99c4-a48aaf6384d2@huawei.com>


> On 2025/5/23 14:45, Dong Chenchen wrote:
>
>>   
>>   static bool page_pool_recycle_in_ring(struct page_pool *pool, netmem_ref netmem)
>>   {
>> +	bool in_softirq;
>>   	int ret;
> int -> bool?

Thanks for your review!

v2 will fix it.

>>   	/* BH protection not needed if current is softirq */
>> -	if (in_softirq())
>> -		ret = ptr_ring_produce(&pool->ring, (__force void *)netmem);
>> -	else
>> -		ret = ptr_ring_produce_bh(&pool->ring, (__force void *)netmem);
>> -
>> -	if (!ret) {
>> +	in_softirq = page_pool_producer_lock(pool);
>> +	ret = !__ptr_ring_produce(&pool->ring, (__force void *)netmem);
>> +	if (ret)
>>   		recycle_stat_inc(pool, ring);
>> -		return true;
>> -	}
>> +	page_pool_producer_unlock(pool, in_softirq);
>>   
>> -	return false;
>> +	return ret;
>>   }
>>   
>>   /* Only allow direct recycling in special circumstances, into the
>> @@ -1091,10 +1088,14 @@ static void page_pool_scrub(struct page_pool *pool)
>>   
>>   static int page_pool_release(struct page_pool *pool)
>>   {
>> +	bool in_softirq;
>>   	int inflight;
>>   
>>   	page_pool_scrub(pool);
>>   	inflight = page_pool_inflight(pool, true);
>> +	/* Acquire producer lock to make sure producers have exited. */
>> +	in_softirq = page_pool_producer_lock(pool);
>> +	page_pool_producer_unlock(pool, in_softirq);
> Is a compiler barrier needed to ensure compiler doesn't optimize away
> the above code?

All the code logic of this function accesses the pool. Do we need to
add a compiler barrier for it?

Best Regards,
Dong Chenchen

>>   	if (!inflight)
>>   		__page_pool_destroy(pool);
>>   

  parent reply	other threads:[~2025-05-26 14:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23  6:45 [PATCH net] page_pool: Fix use-after-free in page_pool_recycle_in_ring Dong Chenchen
2025-05-23  8:30 ` Yunsheng Lin
2025-05-23 16:45   ` Mina Almasry
2025-05-26 14:47     ` dongchenchen (A)
2025-05-26 17:51       ` Mina Almasry
2025-05-27  1:52         ` dongchenchen (A)
2025-05-27  2:13           ` Mina Almasry
2025-05-26 14:27   ` dongchenchen (A) [this message]
2025-05-23  9:16 ` Toke Høiland-Jørgensen
2025-05-23 13:31 ` Paolo Abeni
2025-05-26 15:02   ` dongchenchen (A)
2025-05-23 21:23 ` kernel test robot

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=2c4a2655-2e0d-4c16-82e6-2d9d33d5a276@huawei.com \
    --to=dongchenchen2@huawei.com \
    --cc=almasrymina@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linyunsheng@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+204a4382fcb3311f3858@syzkaller.appspotmail.com \
    --cc=zhangchangzhong@huawei.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