From: Dan Carpenter <dan.carpenter@oracle.com>
To: Bernard f6bvp <f6bvp@free.fr>
Cc: duoming@zju.edu.cn, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, linux-hams@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, ralf@linux-mips.org
Subject: Re: [PATCH net v6] net: rose: fix null-ptr-deref caused by rose_kill_by_neigh
Date: Thu, 14 Jul 2022 17:23:57 +0300 [thread overview]
Message-ID: <20220714142357.GW2338@kadam> (raw)
In-Reply-To: <4c604039-ffb8-bca3-90bb-d8014249c9a2@free.fr>
On Thu, Jul 14, 2022 at 04:11:44PM +0200, Bernard f6bvp wrote:
> Hi,
>
> I am an oldtimer FPAC / ROSE user and occasionnally debugger.
>
> Let me take this opportunity to report a major issue present in rose module
> since kernel 5.4.83 (5.5.10).
Do you think you going do a git bisect to find the buggy patch?
https://wiki.gentoo.org/wiki/Kernel_git-bisect
We should probably start a new email thread for that issue.
regards,
dan carpenter
next prev parent reply other threads:[~2022-07-14 14:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 1:31 [PATCH net v6] net: rose: fix null-ptr-deref caused by rose_kill_by_neigh Duoming Zhou
2022-07-12 11:00 ` Paolo Abeni
2022-07-13 7:50 ` duoming
2022-07-13 8:33 ` Paolo Abeni
2022-07-13 9:03 ` duoming
2022-07-14 14:11 ` Bernard f6bvp
2022-07-14 14:23 ` Dan Carpenter [this message]
[not found] ` <ab0eac7b-3041-6772-21dd-273e1b8fc43e@free.fr>
2022-07-15 22:43 ` [PATCH] net: rose: fix unregistered netdevice: waiting for rose0 to become free Jakub Kicinski
2022-07-22 16:41 ` Bernard f6bvp
2022-07-22 17:05 ` Eric Dumazet
2022-07-23 9:55 ` Bernard f6bvp
2022-07-23 11:21 ` Bernard F6BVP
2022-07-26 13:44 ` Eric Dumazet
2022-07-22 17:37 ` Jakub Kicinski
2022-07-26 18:25 ` [PATCH 1/1] " Bernard Pidoux
2022-07-27 9:06 ` Eric Dumazet
2022-09-04 22:48 ` f6bvp
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=20220714142357.GW2338@kadam \
--to=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=f6bvp@free.fr \
--cc=kuba@kernel.org \
--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).