All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: syzbot <syzbot+f8c45ccc7d5d45fc5965@syzkaller.appspotmail.com>,
	syzkaller-bugs@googlegroups.com,
	Muchun Song <songmuchun@bytedance.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Dmitry Vyukov <dvyukov@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] general protection fault in list_lru_add
Date: Fri, 25 Mar 2022 06:47:36 +0100	[thread overview]
Message-ID: <12984828.uLZWGnKmhe@leap> (raw)
In-Reply-To: <CAHk-=whxaFX4nqnE-SLHTGKyqejvbrhYx5sagcxWd+UWCMf8dg@mail.gmail.com>

On giovedì 24 marzo 2022 20:45:00 CET Linus Torvalds wrote:
> On Thu, Mar 24, 2022 at 12:41 PM syzbot
> <syzbot+f8c45ccc7d5d45fc5965@syzkaller.appspotmail.com> wrote:
> >
> > syzbot has tested the proposed patch and the reproducer did not trigger any issue:
> 
> Heh, well that's unfortunate.
> 
> I think the issue is that it triggered a new BUG() that didn't match
> the previous NULL pointer dereference, so it thinks things are
> "fixed".
> 
>              Linus
> 
> -- 
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/CAHk-%3DwhxaFX4nqnE-SLHTGKyqejvbrhYx5sagcxWd%2BUWCMf8dg%40mail.gmail.com.
> 

No, not at all, Linus!

Unless I'm still sleeping with wide open eyes (it's 6.30 AM here), you are misunderstanding 
this message from Syzbot :)

This message means that Syzbot has applied and tested the patch and now is not 
anymore able to trigger any bug. In summation it means that the patch works properly.

Now Muchun should simply submit his patch (the usual way) with a "Fixes:" tag 
and with "Reported-and-tested-by: syzbot+f8c45ccc7d5d45fc5965@syzkaller.appspotmail.com".

Thanks,

Fabio M. De Francesco



  parent reply	other threads:[~2022-03-25  5:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 22:03 [syzbot] general protection fault in list_lru_add syzbot
2022-03-23 23:11 ` Linus Torvalds
2022-03-24  2:18   ` Muchun Song
2022-03-24  3:05     ` Linus Torvalds
2022-03-24  8:44       ` Muchun Song
2022-03-24  8:50         ` Dmitry Vyukov
2022-03-24 16:12           ` Muchun Song
2022-03-24 16:18             ` Dmitry Vyukov
2022-03-24 16:38               ` Muchun Song
2022-03-24 19:44                 ` syzbot
2022-03-24 19:41             ` syzbot
2022-03-24 19:45               ` Linus Torvalds
2022-03-24 19:47                 ` Linus Torvalds
2022-03-25  1:43                   ` Muchun Song
2022-03-25  4:49                     ` syzbot
2022-03-25  5:47                 ` Fabio M. De Francesco [this message]
2022-03-25 12:37                   ` Fabio M. De Francesco
2022-03-25  9:51 ` Muchun Song
2022-03-25 20:29   ` Linus Torvalds
2022-03-27  5:27     ` Muchun Song

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=12984828.uLZWGnKmhe@leap \
    --to=fmdefrancesco@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=songmuchun@bytedance.com \
    --cc=syzbot+f8c45ccc7d5d45fc5965@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=torvalds@linux-foundation.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 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.