From: Jakub Kicinski <kuba@kernel.org>
To: Edward Adam Davis <eadavis@qq.com>
Cc: davem@davemloft.net, edumazet@google.com, eperezma@redhat.com,
horms@kernel.org, jasowang@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mst@redhat.com,
netdev@vger.kernel.org, pabeni@redhat.com, sgarzare@redhat.com,
stefanha@redhat.com,
syzbot+ci3edb9412aeb2e703@syzkaller.appspotmail.com,
syzbot@lists.linux.dev, syzbot@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, virtualization@lists.linux.dev,
xuanzhuo@linux.alibaba.com
Subject: Re: [PATCH net-next V3] net: restore the iterator to its original state when an error occurs
Date: Thu, 11 Dec 2025 14:21:42 +0900 [thread overview]
Message-ID: <20251211142142.18a4a0b2@kernel.org> (raw)
In-Reply-To: <tencent_000364896CA3A544481764D76486C0336005@qq.com>
On Wed, 10 Dec 2025 18:03:14 +0800 Edward Adam Davis 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.
> The test results [T2] for this version of the patch do not show any
> failures related to zerocopy.
next prev parent reply other threads:[~2025-12-11 5:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 16:03 [PATCH net-next V3] net: restore the iterator to its original state when an error occurs Edward Adam Davis
2025-12-10 8:31 ` Jakub Kicinski
2025-12-10 10:03 ` Edward Adam Davis
2025-12-11 5:21 ` Jakub Kicinski [this message]
2025-12-11 6:32 ` Edward Adam Davis
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=20251211142142.18a4a0b2@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=eadavis@qq.com \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=syzbot+ci3edb9412aeb2e703@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzbot@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).