All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+db0356b67c48887188e2@syzkaller.appspotmail.com>
To: amir73il@gmail.com, linux-kernel@vger.kernel.org,
	 linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
	 syzkaller-bugs@googlegroups.com
Subject: [syzbot] [overlayfs?] WARNING in ovl_create_real (2)
Date: Thu, 12 Dec 2024 19:32:18 -0800	[thread overview]
Message-ID: <675baac2.050a0220.cd16f.003c.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    62b5a46999c7 Merge tag '6.13-rc1-smb3-client-fixes' of git..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1479cb30580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b33c8d5f5a10b30b
dashboard link: https://syzkaller.appspot.com/bug?extid=db0356b67c48887188e2
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-62b5a469.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5982feeea069/vmlinux-62b5a469.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7d4d78f5f270/bzImage-62b5a469.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+db0356b67c48887188e2@syzkaller.appspotmail.com

overlayfs: ...falling back to redirect_dir=nofollow.
overlayfs: ...falling back to index=off.
overlayfs: ...falling back to uuid=null.
------------[ cut here ]------------
WARNING: CPU: 2 PID: 9939 at fs/overlayfs/dir.c:213 ovl_create_real+0x5ab/0x670 fs/overlayfs/dir.c:213
Modules linked in:
CPU: 2 UID: 0 PID: 9939 Comm: syz.1.1043 Not tainted 6.13.0-rc1-syzkaller-00378-g62b5a46999c7 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:ovl_create_real+0x5ab/0x670 fs/overlayfs/dir.c:213
Code: 89 e2 48 c7 c6 80 9b 89 8b 48 c7 c7 50 34 0d 90 e8 ba 23 bb 01 e9 d9 fb ff ff e8 00 5b ef fe e9 93 fc ff ff e8 06 a5 8c fe 90 <0f> 0b 90 4c 89 e3 49 c7 c4 fb ff ff ff e9 d5 fc ff ff e8 7e 38 0e
RSP: 0018:ffffc90023f8fc28 EFLAGS: 00010287
RAX: 00000000000051e1 RBX: ffff8880009de178 RCX: ffffc9000c001000
RDX: 0000000000080000 RSI: ffffffff830c9b7a RDI: ffff8880009de1e0
RBP: 1ffff920047f1f86 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000004 R12: ffff8880009de178
R13: 0000000000000000 R14: ffff888012c0b9f0 R15: 000000000000a000
FS:  0000000000000000(0000) GS:ffff88802b600000(0063) knlGS:00000000f5166b40
CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 000000000c33e9c8 CR3: 000000005d116000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ovl_create_upper fs/overlayfs/dir.c:334 [inline]
 ovl_create_or_link+0x2a4/0x800 fs/overlayfs/dir.c:632
 ovl_create_object+0x268/0x300 fs/overlayfs/dir.c:673
 vfs_symlink fs/namei.c:4669 [inline]
 vfs_symlink+0x3e8/0x660 fs/namei.c:4653
 do_symlinkat+0x263/0x310 fs/namei.c:4695
 __do_sys_symlink fs/namei.c:4716 [inline]
 __se_sys_symlink fs/namei.c:4714 [inline]
 __ia32_sys_symlink+0x74/0x90 fs/namei.c:4714
 do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline]
 __do_fast_syscall_32+0x73/0x120 arch/x86/entry/common.c:386
 do_fast_syscall_32+0x32/0x80 arch/x86/entry/common.c:411
 entry_SYSENTER_compat_after_hwframe+0x84/0x8e
RIP: 0023:0xf747e579
Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000f516657c EFLAGS: 00000292 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00000000200003c0 RCX: 0000000020000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000296 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
----------------
Code disassembly (best guess), 2 bytes skipped:
   0:	10 06                	adc    %al,(%rsi)
   2:	03 74 b4 01          	add    0x1(%rsp,%rsi,4),%esi
   6:	10 07                	adc    %al,(%rdi)
   8:	03 74 b0 01          	add    0x1(%rax,%rsi,4),%esi
   c:	10 08                	adc    %cl,(%rax)
   e:	03 74 d8 01          	add    0x1(%rax,%rbx,8),%esi
  1e:	00 51 52             	add    %dl,0x52(%rcx)
  21:	55                   	push   %rbp
  22:	89 e5                	mov    %esp,%ebp
  24:	0f 34                	sysenter
  26:	cd 80                	int    $0x80
* 28:	5d                   	pop    %rbp <-- trapping instruction
  29:	5a                   	pop    %rdx
  2a:	59                   	pop    %rcx
  2b:	c3                   	ret
  2c:	90                   	nop
  2d:	90                   	nop
  2e:	90                   	nop
  2f:	90                   	nop
  30:	8d b4 26 00 00 00 00 	lea    0x0(%rsi,%riz,1),%esi
  37:	8d b4 26 00 00 00 00 	lea    0x0(%rsi,%riz,1),%esi


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

                 reply	other threads:[~2024-12-13  3:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=675baac2.050a0220.cd16f.003c.GAE@google.com \
    --to=syzbot+db0356b67c48887188e2@syzkaller.appspotmail.com \
    --cc=amir73il@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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.