From: syzbot <syzbot+325b61d3c9a17729454b@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, sandeen@sandeen.net,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] possible deadlock in hfsplus_file_extend
Date: Wed, 09 Oct 2024 16:23:02 -0700 [thread overview]
Message-ID: <67071056.050a0220.67064.0056.GAE@google.com> (raw)
In-Reply-To: <65233b0c-cf11-4ef6-957c-e0434742d6e8@sandeen.net>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
SYZFAIL: NL802154_CMD_SET_SHORT_ADDR failed
2024/10/09 23:22:11 ignoring optional flag "type"="gce"
2024/10/09 23:22:11 parsed 1 programs
2024/10/09 23:22:11 [FATAL] failed to run ["./syz-executor" "setup" "fault" "binfmt_misc" "usb" "802154" "swap"]: exit status 67
mkdir(/syzcgroup) failed: 17
mount(binfmt_misc) failed: 16
SYZFAIL: NL802154_CMD_SET_SHORT_ADDR failed
(errno 16: Device or resource busy)
Tested on:
commit: ffcd06b6 hfs: convert hfs to use the new mount api
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=17b18f07980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8420a89323bff217
dashboard link: https://syzkaller.appspot.com/bug?extid=325b61d3c9a17729454b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
next parent reply other threads:[~2024-10-09 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65233b0c-cf11-4ef6-957c-e0434742d6e8@sandeen.net>
2024-10-09 23:23 ` syzbot [this message]
2024-04-24 16:12 [syzbot] possible deadlock in hfsplus_file_extend Jeongjun Park
2024-04-24 23:38 ` [syzbot] [hfs?] " syzbot
-- strict thread matches above, loose matches on Subject: below --
2022-11-26 8:07 [syzbot] " syzbot
2024-09-28 3:15 ` [syzbot] [hfs?] " syzbot
2024-10-08 6:18 ` Chao Yu
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=67071056.050a0220.67064.0056.GAE@google.com \
--to=syzbot+325b61d3c9a17729454b@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox