From: Jakub Kicinski <kuba@kernel.org>
To: duoming@zju.edu.cn
Cc: linux-hams@vger.kernel.org, pabeni@redhat.com,
ralf@linux-mips.org, davem@davemloft.net, edumazet@google.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v5] net: rose: fix null-ptr-deref caused by rose_kill_by_neigh
Date: Mon, 11 Jul 2022 10:49:49 -0700 [thread overview]
Message-ID: <20220711104949.3de90fc5@kernel.org> (raw)
In-Reply-To: <56319300.38660.181e861b71b.Coremail.duoming@zju.edu.cn>
Hi Duoming!
Unrelated to this particular patch, but it seems like you're working
a lot on AF_ROSE, would you consider adding a good set of selftests
for it? It'd be easier to you to validate the changes and much easier
for us to trust the fixes seeing how they were validated.
next prev parent reply other threads:[~2022-07-11 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 13:52 [PATCH net v5] net: rose: fix null-ptr-deref caused by rose_kill_by_neigh duoming
2022-07-11 17:49 ` Jakub Kicinski [this message]
2022-07-12 0:08 ` duoming
-- strict thread matches above, loose matches on Subject: below --
2022-07-02 7:57 Duoming Zhou
2022-07-05 8:43 ` Paolo Abeni
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=20220711104949.3de90fc5@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ralf@linux-mips.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).