From: syzbot <syzbot+60864ed35b1073540d57@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Write in udf_close_lvid
Date: Tue, 24 May 2022 00:49:11 -0700 [thread overview]
Message-ID: <00000000000042b21705dfbd3128@google.com> (raw)
In-Reply-To: <20220524073044.3421-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: rcu detected stall in corrupted
rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P4150 } 4 jiffies s: 2565 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):
IPv6: ADDRCONF(NETDEV_CHANGE): team0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): hsr_slave_0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): hsr_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): hsr0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_virt_wifi: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_vlan: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vlan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vlan1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Bluetooth: hci1: command 0x0409 tx timeout
Tested on:
commit: 143a6252 Merge tag 'arm64-upstream' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=147795e5f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=dc73592fcf812ebf
dashboard link: https://syzkaller.appspot.com/bug?extid=60864ed35b1073540d57
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=147d0ad6f00000
next parent reply other threads:[~2022-05-24 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220524073044.3421-1-hdanton@sina.com>
2022-05-24 7:49 ` syzbot [this message]
[not found] <20220528073417.3900-1-hdanton@sina.com>
2022-05-28 7:53 ` [syzbot] KASAN: use-after-free Write in udf_close_lvid syzbot
[not found] <20220524044832.3351-1-hdanton@sina.com>
2022-05-24 5:10 ` syzbot
2022-05-24 0:17 syzbot
2022-05-24 10:32 ` Jan Kara
2022-05-24 10:46 ` Pali Rohár
2022-05-24 11:37 ` Jan Kara
2022-05-24 14:43 ` Dmitry Vyukov
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=00000000000042b21705dfbd3128@google.com \
--to=syzbot+60864ed35b1073540d57@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--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.