BPF List
 help / color / mirror / Atom feed
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 15:42:55 +0200	[thread overview]
Message-ID: <Yt1MX1Z6z0y82i1I@kroah.com> (raw)
In-Reply-To: <CANX2M5bxA5FF2Z8PFFc2p-OxkhOJQ8y=8PGF1kdLsJo+C92_gQ@mail.gmail.com>

On Sun, Jul 24, 2022 at 12:40:09AM -0700, Dipanjan Das wrote:
> On Sun, Jul 24, 2022 at 12:26 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > 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:
> 
> We will try to root cause the issue and provide a fix, if possible.
> 
> >
> > > ======================================================
> > > 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.
> 
> Since 5.4.206 is a longterm release kernel, we were under the
> impression that the community is still accepting fixes and patches for
> the same. I understand that adding another bug to the already pending
> queue of syzbot reported issues is not going to help the developers
> much. Therefore, we will definitely try our best to analyze the issue
> and provide a fix in the coming days. Can you please confirm that it
> is worth the effort for the longterm release kernels?

It is worth the effort if the problem is still in the latest kernel
release as that is the only place that new development happens.  If the
issue is not reproducible on Linus's current releases, then finding the
change that solved the problem is also good so that we can then backport
it to the stable/long term kernel release for everyone to benefit from.

So does your reproducer still work on the latest 5.19-rc7 release?

thanks,

greg k-h

  reply	other threads:[~2022-07-24 13:43 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
2022-07-24  7:40   ` Dipanjan Das
2022-07-24 13:42     ` Greg KH [this message]
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=Yt1MX1Z6z0y82i1I@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox