All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: rgerganov@vmware.com,
	syzbot <syzbot+f58fe4bb535845237057@syzkaller.appspotmail.com>,
	gregkh <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: general protection fault in qp_release_pages
Date: Mon, 12 Oct 2020 11:16:22 +0200	[thread overview]
Message-ID: <CAK8P3a28w8kw9MJVx_Cada3c8tQBHT0xXheS2EmGdRgT=2jp6Q@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+aXuBZbvwM1xJNPhG+dHCdjt_Are=p6wRwOk-DFHEGz2Q@mail.gmail.com>

On Mon, Oct 12, 2020 at 10:14 AM Dmitry Vyukov <dvyukov@google.com> wrote:
> On Mon, Oct 12, 2020 at 10:01 AM Arnd Bergmann <arnd@arndb.de> wrote:
> > On Mon, Oct 12, 2020 at 8:11 AM syzbot
> >
> > Adding everyone from the git history that did meaningful changes in the past
> > for this driver, as there is no specific maintainer file entry for
> > them to further
> > investigate.
>
> Hi Arnd,
>
> There is already a recorded fix for this on the dashboard:

Ok, good.

> https://syzkaller.appspot.com/bug?extid=f58fe4bb535845237057
> VMCI: check return value of get_user_pages_fast() for errors

Ah, I actually looked at linux-next, which included the fix. I had
never before looked at the dashboard, good to know where to find
this information.

If this is something that happened to others as well, could the
email report be changed to point out bugs that are already
fixed in linux-next but not in mainline?

     Arnd

  reply	other threads:[~2020-10-12  9:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12  6:11 general protection fault in qp_release_pages syzbot
2020-10-12  8:00 ` Arnd Bergmann
2020-10-12  8:14   ` Dmitry Vyukov
2020-10-12  9:16     ` Arnd Bergmann [this message]
2020-10-12  9:29       ` Dmitry Vyukov
2020-10-12  9:51         ` Arnd Bergmann
2020-10-13 10:35           ` Dmitry Vyukov

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='CAK8P3a28w8kw9MJVx_Cada3c8tQBHT0xXheS2EmGdRgT=2jp6Q@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=dvyukov@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgerganov@vmware.com \
    --cc=syzbot+f58fe4bb535845237057@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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.