From: syzbot <syzbot+7536f77535e5210a5c76@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [tomoyo?] WARNING in tomoyo_write_control
Date: Sun, 15 Dec 2024 23:33:02 -0800 [thread overview]
Message-ID: <675fd7ae.050a0220.37aaf.011a.GAE@google.com> (raw)
In-Reply-To: <20241216071906.2506927-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING: lock held when returning to user space in tomoyo_write_control
================================================
WARNING: lock held when returning to user space!
6.13.0-rc3-syzkaller-g78d4f34e2115-dirty #0 Not tainted
------------------------------------------------
syz.0.16/6711 is leaving the kernel with locks still held!
1 lock held by syz.0.16/6711:
#0: ffff88802a08b080 (&head->io_sem){+.+.}-{4:4}, at: tomoyo_write_control+0x51/0x1b0 security/tomoyo/common.c:2657
Tested on:
commit: 78d4f34e Linux 6.13-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12d7d4f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9cac7e24ceea492
dashboard link: https://syzkaller.appspot.com/bug?extid=7536f77535e5210a5c76
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=12eb1730580000
next parent reply other threads:[~2024-12-16 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241216071906.2506927-1-lizhi.xu@windriver.com>
2024-12-16 7:33 ` syzbot [this message]
[not found] <20241216072034.2513188-1-lizhi.xu@windriver.com>
2024-12-16 7:53 ` [syzbot] [tomoyo?] WARNING in tomoyo_write_control syzbot
2024-12-15 21:48 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=675fd7ae.050a0220.37aaf.011a.GAE@google.com \
--to=syzbot+7536f77535e5210a5c76@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.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.