From: bugzilla-daemon--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 219484] f2fs discard causes kernel NULL pointer dereferencing
Date: Thu, 21 Nov 2024 09:50:24 +0000 [thread overview]
Message-ID: <bug-219484-202145-PZKaMPaXrD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219484-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219484
--- Comment #6 from Chao Yu (chao@kernel.org) ---
Sorry for long delay due to I'm out of office.
Now, I can reproduce this bug w/ below testcase:
- pvcreate /dev/vdb
- vgcreate myvg1 /dev/vdb
- lvcreate -L 1024m -n mylv1 myvg1
- mount /dev/myvg1/mylv1 /mnt/f2fs
- dd if=/dev/zero of=/mnt/f2fs/file bs=1M count=20
- sync
- rm /mnt/f2fs/file
- sync
- lvcreate -L 1024m -s -n mylv1-snapshot /dev/myvg1/mylv1
- umount /mnt/f2fs
------------[ cut here ]------------
kernel BUG at fs/f2fs/segment.c:1363!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 4 UID: 0 PID: 730 Comm: umount Not tainted 6.12.0-rc3+ #1107
RIP: 0010:__submit_discard_cmd+0xa53/0x1410
<TASK>
__issue_discard_cmd+0x3e5/0x1190
f2fs_issue_discard_timeout+0x244/0x360
f2fs_put_super+0x1fc/0xed0
generic_shutdown_super+0x14c/0x4a0
kill_block_super+0x40/0x90
kill_f2fs_super+0x264/0x430
Let me figure out a patch for that soon.:)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-11-21 9:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 12:01 [f2fs-dev] [Bug 219484] New: f2fs discard causes kernel NULL pointer dereferencing bugzilla-daemon--- via Linux-f2fs-devel
2024-11-09 15:11 ` [f2fs-dev] [Bug 219484] " bugzilla-daemon--- via Linux-f2fs-devel
2024-11-09 15:40 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-11-10 11:36 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-11-10 14:44 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-11-10 15:42 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-11-21 9:50 ` bugzilla-daemon--- via Linux-f2fs-devel [this message]
2024-11-21 9:54 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-11-22 22:45 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-12-12 18:57 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-12-17 13:39 ` bugzilla-daemon--- via Linux-f2fs-devel
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=bug-219484-202145-PZKaMPaXrD@https.bugzilla.kernel.org/ \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=bugzilla-daemon@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