https://bugzilla.kernel.org/show_bug.cgi?id=219484
--- Comment #3 from piergiorgio.sar...@nexgo.de ---
One more thing, possibly important.
When I create the snapshot, with the working kernel, while
"max_discard_segments" is still "1", the other two, "discard_max_bytes" and
"discard_max_hw_bytes"
https://bugzilla.kernel.org/show_bug.cgi?id=219484
--- Comment #4 from Chao Yu (c...@kernel.org) ---
Do we have any chance to apply this and try to check whether it can fix this
bug?
From: Chao Yu
---
fs/f2fs/segment.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/fs/f2fs/segment.c b
https://bugzilla.kernel.org/show_bug.cgi?id=219484
--- Comment #5 from piergiorgio.sar...@nexgo.de ---
Thanks for the support.
Difficult to check the patch, I'll have to see with this PC what can I do (not
so free to use).
Which kernel would be this 6.11.5/6/7?
Any other way to test?
For example
https://bugzilla.kernel.org/show_bug.cgi?id=219484
Bug ID: 219484
Summary: f2fs discard causes kernel NULL pointer dereferencing
Product: File System
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Seve
https://bugzilla.kernel.org/show_bug.cgi?id=219484
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=219484
--- Comment #2 from piergiorgio.sar...@nexgo.de ---
Thanks for the prompt reply.
Actually, there is no "max_hw_discard_sectors", but only a
"max_discard_segments", which is "1" (for all DM devices).
It is also "1" for the underlying SSD (/dev/sda
https://bugzilla.kernel.org/show_bug.cgi?id=219484
--- Comment #6 from Chao Yu (c...@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/
https://bugzilla.kernel.org/show_bug.cgi?id=219484
--- Comment #7 from Chao Yu (c...@kernel.org) ---
(In reply to piergiorgio.sartor from comment #3)
> One more thing, possibly important.
>
> When I create the snapshot, with the working kernel, while
> "max_discard_segments" is still "1", the oth
https://bugzilla.kernel.org/show_bug.cgi?id=219586
--- Comment #3 from Jaegeuk Kim (jaeg...@kernel.org) ---
IMO, you need to revert unicode patch.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=219586
--- Comment #2 from HanQi (ha...@vivo.com) ---
(In reply to Jaegeuk Kim from comment #1)
> Hi,
>
> I think that unicode patch introduced a regression, as old and new paths
> gives a different file length. Wasn't that broken to fix?
Hi Kim,
I'm u
https://bugzilla.kernel.org/show_bug.cgi?id=219586
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
Bisected commit-id||18b5f47e7da46d3a0d7331
https://bugzilla.kernel.org/show_bug.cgi?id=219586
Bug ID: 219586
Summary: Unable to find file after unicode change
Product: File System
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: blocking
https://bugzilla.kernel.org/show_bug.cgi?id=219586
--- Comment #1 from Jaegeuk Kim (jaeg...@kernel.org) ---
Hi,
I think that unicode patch introduced a regression, as old and new paths gives
a different file length. Wasn't that broken to fix?
--
You may reply to this email to add a comment.
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=219586
Paul Menzel (pmenzel+bugzilla.kernel@molgen.mpg.de) changed:
What|Removed |Added
CC||
https://bugzilla.kernel.org/show_bug.cgi?id=219586
HanQi (ha...@vivo.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=219586
--- Comment #5 from Chao Yu (c...@kernel.org) ---
(In reply to HanQi from comment #0)
> Hi everybody,
> The f2fs filesystem is unable to read some files with special characters,
> such as ❤️, after the kernel was updated with the following patch:
https://bugzilla.kernel.org/show_bug.cgi?id=219484
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|-
https://bugzilla.kernel.org/show_bug.cgi?id=219484
--- Comment #9 from piergiorgio.sar...@nexgo.de ---
Hi all,
I tested kernel-6.12.4-100.fc40.x86_64.rpm (Fedora 40, Koji build).
This is supposed to include the patch and, for what I tested, it seems to work
fine. No NULL pointer de-referencing, n
https://bugzilla.kernel.org/show_bug.cgi?id=219586
--- Comment #6 from HanQi (ha...@vivo.com) ---
(In reply to Chao Yu from comment #5)
> (In reply to HanQi from comment #0)
> > Hi everybody,
> > The f2fs filesystem is unable to read some files with special characters,
> > such as ❤️, after the ke
https://bugzilla.kernel.org/show_bug.cgi?id=219484
--- Comment #8 from piergiorgio.sar...@nexgo.de ---
Thanks for taking the time to reproduce the issue.
I tried to compile the kernel with your patch, but it seems these days is not
anymore as easy as it used to be. No success...
Good the you manag
https://bugzilla.kernel.org/show_bug.cgi?id=219784
Bug ID: 219784
Summary: RIP: 0010:__list_add_valid_or_report.cold+0x4f/0x60
Product: File System
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity
https://bugzilla.kernel.org/show_bug.cgi?id=219784
sander44 (ionut_n2...@yahoo.com) changed:
What|Removed |Added
Kernel Version||6.13.2
--
You may rep
https://bugzilla.kernel.org/show_bug.cgi?id=219784
--- Comment #1 from sander44 (ionut_n2...@yahoo.com) ---
Created attachment 307661
--> https://bugzilla.kernel.org/attachment.cgi?id=307661&action=edit
dmesg 6.13.2
--
You may reply to this email to add a comment.
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=219784
--- Comment #2 from sander44 (ionut_n2...@yahoo.com) ---
# lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root
Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU
00:01.0 Host bridge: Advanc
https://bugzilla.kernel.org/show_bug.cgi?id=219784
--- Comment #3 from sander44 (ionut_n2...@yahoo.com) ---
Maybe exist one regression in 6.13.2/6.13 branch.
I will go back to the 6.12/6.12.0 branch to test more things.
--
You may reply to this email to add a comment.
You are receiving this ma
https://bugzilla.kernel.org/show_bug.cgi?id=219784
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
--- Comment #
https://bugzilla.kernel.org/show_bug.cgi?id=220321
--- Comment #2 from SEO HOYOUNG (hy50@samsung.com) ---
Yes.
A problem occurred when quota_release_work used a workqueue without
WQ_MEM_RECLAIM flag.
So I think we should use workqueue with WQ_MEM_RECLAIM flag.
The WQ_MEM_RECLAIM flag cannot be
https://bugzilla.kernel.org/show_bug.cgi?id=220321
Bug ID: 220321
Summary: F2FS: workqueue: WQ_MEM_RECLAIM writeback:wb_workfn is
flushing !WQ_MEM_RECLAIM
events_unbound:quota_release_workfn
Product: File System
V
https://bugzilla.kernel.org/show_bug.cgi?id=220321
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
--- Comment #
https://bugzilla.kernel.org/show_bug.cgi?id=220321
--- Comment #4 from Chao Yu (c...@kernel.org) ---
Sorry for the delay.
The workqueue is not allocated by f2fs, not sure this is a f2fs bug...
Can you please report this issue to fsdevel mailing list:
linux-fsde...@vger.kernel.org?
--
You may r
https://bugzilla.kernel.org/show_bug.cgi?id=220321
--- Comment #3 from SEO HOYOUNG (hy50@samsung.com) ---
Our development system occurred this problem again.
It seems that write data to f2fs using write back option.
The wb_wrokfn function use writeback workqueue.
And the writeback workqueue c
https://bugzilla.kernel.org/show_bug.cgi?id=220321
--- Comment #5 from SEO HOYOUNG (hy50@samsung.com) ---
Hi, I uploaded to mainline fix patch.
But I do not know it is right.
https://lore.kernel.org/linux-scsi/20250721064024.113841-1-hy50@samsung.com/T/#u
I thought of another way, how ab
https://bugzilla.kernel.org/show_bug.cgi?id=220321
SEO HOYOUNG (hy50@samsung.com) changed:
What|Removed |Added
Component|f2fs|devfs
--
You may re
https://bugzilla.kernel.org/show_bug.cgi?id=220124
Bug ID: 220124
Summary: overlayfs
Product: File System
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
C
https://bugzilla.kernel.org/show_bug.cgi?id=220124
w5...@outlook.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Component|f2fs
https://bugzilla.kernel.org/show_bug.cgi?id=220575
Bug ID: 220575
Summary: Unable to handle kernel NULL pointer dereference at
virtual address
Product: File System
Version: 2.5
Kernel Version: 6.12.30-android16
https://bugzilla.kernel.org/show_bug.cgi?id=220575
--- Comment #3 from Chao Yu (c...@kernel.org) ---
I meant using trace32 to dump field value of victim page, something like that.
:)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assig
https://bugzilla.kernel.org/show_bug.cgi?id=220575
--- Comment #2 from JY (jy...@mediatek.com) ---
(In reply to Chao Yu from comment #1)
> Hi,
>
> Do you have a ramdump about this issue, if there is, can you please provide
> more information about the corrupted page?
>
> Thanks,
Hi Chao,
Do yo
https://bugzilla.kernel.org/show_bug.cgi?id=220575
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
--- Comment #
https://bugzilla.kernel.org/show_bug.cgi?id=220575
--- Comment #8 from JY (jy...@mediatek.com) ---
OK, I will try it.
At the last experiment, I used the newly added '_private' to record non-null
value and dump it when fscrypt_is_bounce_page(page) is true.
+ pr_crit("bounced_page:0x
https://bugzilla.kernel.org/show_bug.cgi?id=220575
--- Comment #9 from JY (jy...@mediatek.com) ---
Oh NO...
I saw my fault...
static inline void set_page_private(...)
{
page->private = private;
+ if (!private) <<< :(
+ page->_private = private;
}
It s
https://bugzilla.kernel.org/show_bug.cgi?id=220575
--- Comment #5 from Chao Yu (c...@kernel.org) ---
If this is reproducible, could you check whether we're suffer panic in
f2fs_submit_page_bio()? if it is, could you please have a try w/ below fix:
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
inde
https://bugzilla.kernel.org/show_bug.cgi?id=220575
--- Comment #7 from Chao Yu (c...@kernel.org) ---
Can you please hook fscrypt_free_bounce_page() to set page private w/ special
value, something as below:
void fscrypt_free_bounce_page(struct page *bounce_page)
{
if (!bounce_page)
https://bugzilla.kernel.org/show_bug.cgi?id=220575
--- Comment #6 from JY (jy...@mediatek.com) ---
(In reply to Chao Yu from comment #5)
> If this is reproducible, could you check whether we're suffer panic in
> f2fs_submit_page_bio()? if it is, could you please have a try w/ below fix:
>
> diff
https://bugzilla.kernel.org/show_bug.cgi?id=220575
--- Comment #4 from JY (jy...@mediatek.com) ---
(In reply to Chao Yu from comment #3)
> I meant using trace32 to dump field value of victim page, something like
> that. :)
For some reasons, I can't dump the victim page with trace32.
So I'm using
https://bugzilla.kernel.org/show_bug.cgi?id=220575
--- Comment #10 from Chao Yu (c...@kernel.org) ---
Your device is using software encryption, right? If so, page will point to
fio->encrypted_page which is a bounced page.
https://android.googlesource.com/kernel/common/+/e0e2f78243385e7188a57fcfce
46 matches
Mail list logo
