linux-kernel - Re: [PATCH net] virtio_net: adjust the execution order of function `virtnet

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250815060615.4162-1-junnan01.wu@samsung.com>
Date: Fri, 15 Aug 2025 14:06:15 +0800
From: Junnan Wu <junnan01.wu@...sung.com>
To: jasowang@...hat.com
Cc: andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
	eperezma@...hat.com, junnan01.wu@...sung.com, kuba@...nel.org,
	lei19.wang@...sung.com, linux-kernel@...r.kernel.org, mst@...hat.com,
	netdev@...r.kernel.org, pabeni@...hat.com, q1.huang@...sung.com,
	virtualization@...ts.linux.dev, xuanzhuo@...ux.alibaba.com,
	ying123.xu@...sung.com
Subject: Re: [PATCH net] virtio_net: adjust the execution order of function
 `virtnet_close` during freeze

On Fri, 15 Aug 2025 13:38:21 +0800 Jason Wang <jasowang@...hat.com> wrote
> On Fri, Aug 15, 2025 at 10:24 AM Junnan Wu <junnan01.wu@...sung.com> wrote:
> >
> > Sorry, I basically mean that the tx napi which caused by userspace will not be scheduled during suspend,
> > others can not be guaranteed, such as unfinished packets already in tx vq etc.
> >
> > But after this patch, once `virtnet_close` completes,
> > both tx and rq napi will be disabled which guarantee their napi will not be scheduled in future.
> > And the tx state will be set to "__QUEUE_STATE_DRV_XOFF" correctly in `netif_device_detach`.
> 
> Ok, so the commit mentioned by fix tag is incorrect.

Yes, you are right. The commit of this fix tag is the first commit I found which add function `virtnet_poll_cleantx`.
Actually, we are not sure whether this issue appears after this commit.

In our side, this issue is found by chance in version 5.15.

It's hard to find the key commit which cause this issue
for reason that the reproduction of this scenario is too complex.