[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tencent_62102EE16E389458E93EED06CEBC780A6D0A@qq.com>
Date: Thu, 11 Dec 2025 14:32:18 +0800
From: Edward Adam Davis <eadavis@...com>
To: kuba@...nel.org
Cc: davem@...emloft.net,
eadavis@...com,
edumazet@...gle.com,
eperezma@...hat.com,
horms@...nel.org,
jasowang@...hat.com,
kvm@...r.kernel.org,
linux-kernel@...r.kernel.org,
mst@...hat.com,
netdev@...r.kernel.org,
pabeni@...hat.com,
sgarzare@...hat.com,
stefanha@...hat.com,
syzbot+ci3edb9412aeb2e703@...kaller.appspotmail.com,
syzbot@...ts.linux.dev,
syzbot@...kaller.appspotmail.com,
syzkaller-bugs@...glegroups.com,
virtualization@...ts.linux.dev,
xuanzhuo@...ux.alibaba.com
Subject: Re: [PATCH net-next V3] net: restore the iterator to its original state when an error occurs
On Thu, 11 Dec 2025 14:21:42 +0900, Jakub Kicinski wrote:
> > > Have you investigated the other callers? Given problems with previous
> > > version of this patch I'm worried you have not. If you did please extend
> > > the commit message with the appropriate explanation.
> > Are you asking if I investigated other zerocopy tests? NO.
>
> I said callers. You're changing behavior of a function, is it going
> to break any of the callers.
I investigated the relevant callers and found no similar restore/revert
operations. Furthermore, if such a restore action existed, the ZC
related test programs would have detected it, just as the tests
detected the revert operation in skb_zerocopy_iter_stream().
Powered by blists - more mailing lists