From: Greg KH <gregkh@linuxfoundation.org>
To: Dipanjan Das <mail.dipanjan.das@gmail.com>
Cc: davem@davemloft.net, ast@kernel.org, daniel@iogearbox.net,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com, andriin@fb.com,
sashal@kernel.org, edumazet@google.com,
steffen.klassert@secunet.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
syzkaller@googlegroups.com, fleischermarius@googlemail.com,
its.priyanka.bose@gmail.com
Subject: Re: general protection fault in sock_def_error_report
Date: Sun, 24 Jul 2022 09:21:24 +0200 [thread overview]
Message-ID: <Ytzy9IjGXziLaVV0@kroah.com> (raw)
In-Reply-To: <CANX2M5Yphi3JcCsMf3HgPPkk9XCfOKO85gyMdxQf3_O74yc1Hg@mail.gmail.com>
On Sat, Jul 23, 2022 at 03:07:09PM -0700, Dipanjan Das wrote:
> Hi,
>
> We would like to report the following bug which has been found by our
> modified version of syzkaller.
Do you have a fix for this issue? Without that, it's a bit harder as:
> ======================================================
> description: general protection fault in sock_def_error_report
> affected file: net/core/sock.c
> kernel version: 5.4.206
You are using a very old kernel version, and we have loads of other
syzbot-reported issues to resolve that trigger on newer kernels.
thanks,
greg k-h
next prev parent reply other threads:[~2022-07-24 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 22:07 general protection fault in sock_def_error_report Dipanjan Das
2022-07-24 7:21 ` Greg KH [this message]
2022-07-24 7:40 ` Dipanjan Das
2022-07-24 13:42 ` Greg KH
2022-07-28 19:24 ` Dipanjan Das
2022-07-29 7:44 ` Greg KH
2022-07-29 7:47 ` Dipanjan Das
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=Ytzy9IjGXziLaVV0@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fleischermarius@googlemail.com \
--cc=its.priyanka.bose@gmail.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail.dipanjan.das@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=songliubraving@fb.com \
--cc=steffen.klassert@secunet.com \
--cc=syzkaller@googlegroups.com \
--cc=yhs@fb.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.