From: Jakub Kicinski <kuba@kernel.org>
To: Anastasia Kovaleva <a.kovaleva@yadro.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux@yadro.com" <linux@yadro.com>
Subject: Re: [PATCH v2 net] net: Fix an unsafe loop on the list
Date: Wed, 2 Oct 2024 11:56:07 -0700 [thread overview]
Message-ID: <20241002115607.1d689497@kernel.org> (raw)
In-Reply-To: <F4920F6D-1BE9-4268-8301-B69368DD2E1D@yadro.com>
On Wed, 2 Oct 2024 17:53:18 +0000 Anastasia Kovaleva wrote:
> If it is really necessary, it would take me a couple of days to make a test.
The only tricky part, I think, is finding a family which can be easily
unloaded for the test. I don't see any good candidates, so fine.
prev parent reply other threads:[~2024-10-02 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 11:58 [PATCH v2 net] net: Fix an unsafe loop on the list Anastasia Kovaleva
2024-10-02 13:02 ` Jakub Kicinski
2024-10-02 17:53 ` Anastasia Kovaleva
2024-10-02 18:56 ` Jakub Kicinski [this message]
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=20241002115607.1d689497@kernel.org \
--to=kuba@kernel.org \
--cc=a.kovaleva@yadro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@yadro.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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).