All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+016b09736213e65d106e@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
	linux-fsdevel@vger.kernel.org,  linux-kernel@vger.kernel.org,
	llvm@lists.linux.dev, nathan@kernel.org,
	 ndesaulniers@google.com, ntfs3@lists.linux.dev,
	 syzkaller-bugs@googlegroups.com, trix@redhat.com
Subject: Re: [syzbot] [ntfs3?] possible deadlock in ntfs_mark_rec_free (2)
Date: Sat, 09 Nov 2024 00:31:02 -0800	[thread overview]
Message-ID: <672f1dc6.050a0220.138bd5.003b.GAE@google.com> (raw)
In-Reply-To: <0000000000001a94c3061747fabd@google.com>

syzbot suspects this issue was fixed by commit:

commit 5b2db723455a89dc96743d34d8bdaa23a402db2f
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date:   Mon Aug 19 13:26:22 2024 +0000

    fs/ntfs3: Fix warning possible deadlock in ntfs_set_state

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15a67d87980000
start commit:   ea5f6ad9ad96 Merge tag 'platform-drivers-x86-v6.10-1' of g..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=f59c50304274d557
dashboard link: https://syzkaller.appspot.com/bug?extid=016b09736213e65d106e
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=133fa268980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=142cb182980000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: fs/ntfs3: Fix warning possible deadlock in ntfs_set_state

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

  parent reply	other threads:[~2024-11-09  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30  3:29 [syzbot] [ntfs3?] possible deadlock in ntfs_mark_rec_free (2) syzbot
2024-05-17  5:28 ` syzbot
2024-05-17 16:29 ` syzbot
2024-08-23 16:02 ` [syzbot] " syzbot
2024-11-09  8:31 ` syzbot [this message]
     [not found] <5ff534147df14a938c79911a34fd52bf@paragon-software.com>
2024-08-23 16:24 ` [syzbot] [ntfs3?] " syzbot

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=672f1dc6.050a0220.138bd5.003b.GAE@google.com \
    --to=syzbot+016b09736213e65d106e@syzkaller.appspotmail.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=ntfs3@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=trix@redhat.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.