All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+41a88b825a315aac2254@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, eadavis@qq.com,
	ernesto.mnd.fernandez@gmail.com,  linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com,
	torvalds@linux-foundation.org,  willy@infradead.org
Subject: Re: [syzbot] [hfs?] possible deadlock in hfs_extend_file (2)
Date: Tue, 02 Jan 2024 16:40:05 -0800	[thread overview]
Message-ID: <0000000000002dbc50060dffdba0@google.com> (raw)
In-Reply-To: <000000000000d95cf9060c5038e3@google.com>

syzbot has bisected this issue to:

commit 54640c7502e5ed41fbf4eedd499e85f9acc9698f
Author: Ernesto A. Fernández <ernesto.mnd.fernandez@gmail.com>
Date:   Tue Oct 30 22:06:17 2018 +0000

    hfs: prevent btree data loss on ENOSPC

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1121e49ae80000
start commit:   610a9b8f49fb Linux 6.7-rc8
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=1321e49ae80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1521e49ae80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=247b5a935d307ee5
dashboard link: https://syzkaller.appspot.com/bug?extid=41a88b825a315aac2254
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1552fe19e80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1419bcade80000

Reported-by: syzbot+41a88b825a315aac2254@syzkaller.appspotmail.com
Fixes: 54640c7502e5 ("hfs: prevent btree data loss on ENOSPC")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2024-01-03  0:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 13:42 [syzbot] [hfs?] possible deadlock in hfs_extend_file (2) syzbot
2024-01-02  5:11 ` syzbot
2024-01-02 11:37   ` Edward Adam Davis
2024-01-02 12:08     ` syzbot
2024-01-02 12:36   ` [PATCH] hfs: fix deadlock in hfs_extend_file Edward Adam Davis
2024-01-03  7:45     ` Matthew Wilcox
2024-01-03  9:03     ` Viacheslav Dubeyko
2024-01-03  0:40 ` syzbot [this message]
2024-02-22  4:10 ` [syzbot] [hfs?] possible deadlock in hfs_extend_file (2) syzbot
2024-02-22 10:01   ` Jan Kara
  -- strict thread matches above, loose matches on Subject: below --
2024-01-20 14:40 [syzbot] [hfs?] INFO: task hung in hfs_find_init (2) syzbot
2024-01-22  6:43 ` [syzbot] [hfs?] possible deadlock in hfs_extend_file (2) Edward Adam Davis

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=0000000000002dbc50060dffdba0@google.com \
    --to=syzbot+41a88b825a315aac2254@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=eadavis@qq.com \
    --cc=ernesto.mnd.fernandez@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.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.