From: syzbot <syzbot+4125590f2a9f5b3cdf43@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [overlayfs?] WARNING in ovl_listxattr
Date: Thu, 12 Jun 2025 00:37:03 -0700 [thread overview]
Message-ID: <684a839f.050a0220.be214.028c.GAE@google.com> (raw)
In-Reply-To: <20250612071417.2222649-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in ovl_listxattr
WARNING: The mand mount option has been deprecated and
and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================
buf: system.posix_acl_access, size: 182, res: 17, ovl_listxattr
s: system.posix_acl_access, len: 17, slen: 18, ovl_listxattr
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6633 at fs/overlayfs/xattrs.c:138 ovl_listxattr+0x3db/0x430 fs/overlayfs/xattrs.c:138
Modules linked in:
CPU: 1 UID: 0 PID: 6633 Comm: syz.0.16 Not tainted 6.16.0-rc1-syzkaller-g2c4a1f3fe03e-dirty #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:ovl_listxattr+0x3db/0x430 fs/overlayfs/xattrs.c:138
Code: 05 f2 fe e9 47 ff ff ff e8 02 b9 90 fe 4c 89 f8 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 e6 b8 90 fe 90 <0f> 0b 90 49 c7 c7 fb ff ff ff eb d7 e8 d4 b8 90 fe 90 0f 0b 90 e9
RSP: 0018:ffffc900033a7d98 EFLAGS: 00010293
RAX: ffffffff832f950a RBX: ffff888077ba4200 RCX: ffff88802d620000
RDX: 0000000000000000 RSI: 0000000000000011 RDI: 0000000000000012
RBP: ffff88802a27de01 R08: ffffc900033a7ac7 R09: 1ffff92000674f58
R10: dffffc0000000000 R11: fffff52000674f59 R12: ffffffffffffffff
R13: 0000000000000012 R14: ffff8880787a3c88 R15: 0000000000000011
FS: 00007f48fba146c0(0000) GS:ffff888125d86000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000001000 CR3: 000000007c3f0000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
vfs_listxattr fs/xattr.c:493 [inline]
listxattr+0x10a/0x2a0 fs/xattr.c:924
filename_listxattr fs/xattr.c:958 [inline]
path_listxattrat+0x179/0x3a0 fs/xattr.c:988
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f48fab8e969
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f48fba14038 EFLAGS: 00000246 ORIG_RAX: 00000000000000c3
RAX: ffffffffffffffda RBX: 00007f48fadb5fa0 RCX: 00007f48fab8e969
RDX: 00000000000000b6 RSI: 0000200000000200 RDI: 00002000000001c0
RBP: 00007f48fac10ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f48fadb5fa0 R15: 00007ffea266aa98
</TASK>
Tested on:
commit: 2c4a1f3f Merge tag 'bpf-fixes' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15676e0c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=162faeb2d1eaefb4
dashboard link: https://syzkaller.appspot.com/bug?extid=4125590f2a9f5b3cdf43
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
patch: https://syzkaller.appspot.com/x/patch.diff?x=117b6e0c580000
next parent reply other threads:[~2025-06-12 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250612071417.2222649-1-lizhi.xu@windriver.com>
2025-06-12 7:37 ` syzbot [this message]
2025-05-17 9:38 [syzbot] [overlayfs?] WARNING in ovl_listxattr syzbot
2025-06-12 11:32 ` Edward Adam Davis
2025-06-12 13:19 ` syzbot
2025-06-12 13:34 ` Edward Adam Davis
2025-06-12 14:02 ` syzbot
2025-06-12 14:29 ` Edward Adam Davis
2025-06-12 14:59 ` syzbot
2025-07-17 7:47 ` 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=684a839f.050a0220.be214.028c.GAE@google.com \
--to=syzbot+4125590f2a9f5b3cdf43@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.