Linux-f2fs-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 220575] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
Date: Tue, 30 Sep 2025 10:45:11 +0000	[thread overview]
Message-ID: <bug-220575-202145-ySLg8M6sMD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220575-202145@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220575

--- Comment #14 from JY (JY.Ho@mediatek.com) ---
(In reply to Chao Yu from comment #12)
> Hi JY,
> 
> I've figured out a reproducer as below:
> 
> 1. mkdir /mnt/f2fs/enc & encrypt /mnt/f2fs/enc
> 
> 2. Run below script in shell #1:
> for ((i=1;i>0;i++)) do xfs_io -f /mnt/f2fs/enc/file \
> -c "pwrite 0 32k" -c "fdatasync"
> 
> 3. Run below script in shell #2:
> for ((i=1;i>0;i++)) do xfs_io -f /mnt/f2fs/enc/file \
> -c "pwrite 0 32k" -c "fdatasync"
> 
> Now, testing below fix.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/
> ?h=bugfix/syzbot&id=1d024fd4c6fed3767f063db79746bcd2d0be49d1

Hi Chao,

In my kernel version (
https://android.googlesource.com/kernel/common/+/refs/heads/android16-6.12-2025-07/fs/f2fs/data.c#926),
Should I modify:
- inc_page_count(fio->sbi, WB_DATA_TYPE(page, false));
+ inc_page_count(fio->sbi, WB_DATA_TYPE(fio->page, false));
Is that right?

-- 
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

  parent reply	other threads:[~2025-09-30 10:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15  3:33 [f2fs-dev] [Bug 220575] New: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 bugzilla-daemon--- via Linux-f2fs-devel
2025-09-15 12:27 ` [f2fs-dev] [Bug 220575] " bugzilla-daemon--- via Linux-f2fs-devel
2025-09-16  2:19 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-16  2:52 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-24  6:50 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-24  8:47 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-24  9:51 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-24 13:22 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-25  3:38 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-25  3:41 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-25  8:40 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-25  9:23 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-28 10:30 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-28 13:55 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-09-30 10:45 ` bugzilla-daemon--- via Linux-f2fs-devel [this message]
2025-10-01  7:51 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-10-01  8:01 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-10-03  2:33 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-10-03  2:44 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-10-03  3:13 ` 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-220575-202145-ySLg8M6sMD@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