From: syzbot <syzbot+4125590f2a9f5b3cdf43@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [overlayfs?] WARNING in ovl_listxattr
Date: Thu, 12 Jun 2025 00:14:22 -0700 [thread overview]
Message-ID: <684a7e4e.050a0220.be214.028b.GAE@google.com> (raw)
In-Reply-To: <6828591c.a00a0220.398d88.0248.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [overlayfs?] WARNING in ovl_listxattr
Author: lizhi.xu@windriver.com
#syz test
diff --git a/fs/overlayfs/xattrs.c b/fs/overlayfs/xattrs.c
index 88055deca936..69e17db853f5 100644
--- a/fs/overlayfs/xattrs.c
+++ b/fs/overlayfs/xattrs.c
@@ -122,6 +122,7 @@ ssize_t ovl_listxattr(struct dentry *dentry, char *list, size_t size)
old_cred = ovl_override_creds(dentry->d_sb);
res = vfs_listxattr(realdentry, list, size);
ovl_revert_creds(old_cred);
+ printk("buf: %s, size: %lu, res: %ld, %s\n", list, size, res, __func__);
if (res <= 0 || size == 0)
return res;
@@ -131,6 +132,7 @@ ssize_t ovl_listxattr(struct dentry *dentry, char *list, size_t size)
/* filter out private xattrs */
for (s = list, len = res; len;) {
size_t slen = strnlen(s, len) + 1;
+ printk("s: %s, len: %lu, slen: %lu, %s\n", s, len, slen, __func__);
/* underlying fs providing us with an broken xattr list? */
if (WARN_ON(slen > len))
next prev parent reply other threads:[~2025-06-12 7:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 9:38 syzbot
2025-06-12 7:14 ` syzbot [this message]
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-06-12 15:01 ` [PATCH] fs/xattr: reset err to 0 after get security.* xattrs Edward Adam Davis
2025-06-12 15:09 ` Stephen Smalley
2025-07-17 7:47 ` [syzbot] [overlayfs?] WARNING in ovl_listxattr 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=684a7e4e.050a0220.be214.028b.GAE@google.com \
--to=syzbot+4125590f2a9f5b3cdf43@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®