All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandr Nogikh <nogikh@google.com>
To: syzbot <syzbot+bfbc1eecdfb9b10e5792@syzkaller.appspotmail.com>
Cc: dchinner@redhat.com, djwong@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] general protection fault in __xfs_free_extent
Date: Tue, 30 May 2023 11:58:17 +0200	[thread overview]
Message-ID: <CANp29Y6vkDOAbL4T7hBdd-3fjfkM1vAJfhJF2Xw_UHNPEjawLQ@mail.gmail.com> (raw)
In-Reply-To: <0000000000003ccc9b05fcbfdb68@google.com>

On Sun, May 28, 2023 at 2:10 PM syzbot
<syzbot+bfbc1eecdfb9b10e5792@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit b2ccab3199aa7cea9154d80ea2585312c5f6eba0
> Author: Darrick J. Wong <djwong@kernel.org>
> Date:   Wed Apr 12 01:59:53 2023 +0000
>
>     xfs: pass per-ag references to xfs_free_extent
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1007e5c1280000
> start commit:   02bf43c7b7f7 Merge tag 'fs.xattr.simple.rework.rbtree.rwlo..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=8c59170b68d26a55
> dashboard link: https://syzkaller.appspot.com/bug?extid=bfbc1eecdfb9b10e5792
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1798429d880000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=161b948f880000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: xfs: pass per-ag references to xfs_free_extent

Seems reasonable.

#syz fix: xfs: pass per-ag references to xfs_free_extent

>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
> --
> 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/0000000000003ccc9b05fcbfdb68%40google.com.

      reply	other threads:[~2023-05-30  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-18  6:06 [syzbot] general protection fault in __xfs_free_extent syzbot
2023-05-28 12:10 ` [syzbot] [xfs?] " syzbot
2023-05-30  9:58   ` Aleksandr Nogikh [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=CANp29Y6vkDOAbL4T7hBdd-3fjfkM1vAJfhJF2Xw_UHNPEjawLQ@mail.gmail.com \
    --to=nogikh@google.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=syzbot+bfbc1eecdfb9b10e5792@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.