From: Sam Sun <samsun1006219@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, dsahern@kernel.org, kuba@kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
xrivendell7@gmail.com
Subject: Re: [Linux kernel bug] general protection fault in nexthop_is_blackhole
Date: Tue, 7 May 2024 15:39:04 +0800 [thread overview]
Message-ID: <CAEkJfYP9PdD=4kbqWac0ny+X-D5YdZrtqW8VukFak0zRMo+=7Q@mail.gmail.com> (raw)
In-Reply-To: <CANn89iLFvGd+=YCbzm==fA3Q0dj=FC-gTZy3kVJ0DTpZ5hZC8w@mail.gmail.com>
On Tue, May 7, 2024 at 3:31 PM Eric Dumazet <edumazet@google.com> wrote:
>
> On Tue, May 7, 2024 at 9:00 AM Sam Sun <samsun1006219@gmail.com> wrote:
> >
> > Dear developers and maintainers,
> >
> > We encountered a general protection fault in function
> > nexthop_is_blackhole. It was tested against the latest upstream linux
> > (tag 6.9-rc7). C repro and kernel config are attached to this email.
> > Kernel crash log is listed below.
>
> This is another reiserfs bug, please let's not be mistaken.
>
> We have dozens of syzbot reports about reiserfs.
>
> Thank you.
>
Sorry for my mistake and thanks for pointing out. I only checked the
call stack without checking the repro. I will ban the reiserfs in
future testing.
Best Regards,
Yue
prev parent reply other threads:[~2024-05-07 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 7:00 [Linux kernel bug] general protection fault in nexthop_is_blackhole Sam Sun
2024-05-07 7:31 ` Eric Dumazet
2024-05-07 7:39 ` Sam Sun [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='CAEkJfYP9PdD=4kbqWac0ny+X-D5YdZrtqW8VukFak0zRMo+=7Q@mail.gmail.com' \
--to=samsun1006219@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xrivendell7@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.