https://bugzilla.kernel.org/show_bug.cgi?id=200773
--- Comment #1 from Shuaibing Lu (datadan...@163.com) ---
-Location
https://elixir.bootlin.com/linux/v4.17.1/source/fs/f2fs/checkpoint.c#L741
*cp_page = get_meta_page(sbi, cp_addr);
*cp_block = (struct f2fs_checkpoint
https://bugzilla.kernel.org/show_bug.cgi?id=200773
Bug ID: 200773
Summary: An issue was discovered in the Linux kernel through
4.17.3. There is a NULL pointer dereference in
get_checkpoint_version() in fs/f2fs/checkpoint.c when
https://bugzilla.kernel.org/show_bug.cgi?id=200773
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=200871
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=200635
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=200635
--- Comment #1 from Chao Yu (c...@kernel.org) ---
It has been fixed by below commit, can you please check it?
f2fs: fix to do sanity check with cp_pack_start_sum
https://bugzilla.kernel.org/show_bug.cgi?id=200635
Stathis Maneas (sman...@cs.toronto.edu) changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://bugzilla.kernel.org/show_bug.cgi?id=200635
Stathis Maneas (sman...@cs.toronto.edu) changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=200177
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200181
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200223
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200185
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200423
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200167
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=200171
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=200183
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200221
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200419
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200175
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=200465
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200635
--- Comment #4 from Chao Yu (c...@kernel.org) ---
Thanks for reminding that, IMO, yes, after we enable superblock checksum
feature, we can know which sb is corrupted, and try to recovery corrupted sb
with another good one.
Although, for your
https://bugzilla.kernel.org/show_bug.cgi?id=200173
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=200425
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200179
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=200421
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200635
--- Comment #5 from Stathis Maneas (sman...@cs.toronto.edu) ---
For the case where the checksum mechanism is not enabled for the superblock, it
would be nice to fix the error and make the file system able to be mounted once
again, provided that
https://bugzilla.kernel.org/show_bug.cgi?id=200635
--- Comment #6 from Chao Yu (c...@kernel.org) ---
SB checksum feature is not upstreamed yet, and there is one bug in the patch,
could you fix this manually and apply that patchset?
https://sourceforge.net/p/linux-f2fs/mailman/message/36402182/
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #2 from vice...@gmail.com ---
Created attachment 278131
--> https://bugzilla.kernel.org/attachment.cgi?id=278131=edit
sg_vpd
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=200951
Bug ID: 200951
Summary: kernel NULL pointer dereference in update_sit_entry
Product: File System
Version: 2.5
Kernel Version: v4.19-rc1, v4.18.2
Hardware: ARM
OS: Linux
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #1 from vice...@gmail.com ---
Created attachment 278129
--> https://bugzilla.kernel.org/attachment.cgi?id=278129=edit
sg_readcap
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=200871
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #2 from Stathis Maneas (sman...@cs.toronto.edu) ---
1. I am using a device mapper module similar to the existing dm-flakey module:
https://elixir.bootlin.com/linux/v4.18/source/drivers/md/dm-flakey.c
Specifically, an error is
Konstantin Ryabitsev (mri...@kernel.org) has used the 'sudo' feature to
access
Kernel.org Bugzilla using your account.
Konstantin Ryabitsev (mri...@kernel.org) provided the following reason for
doing this:
Adding bugmail per RT#58184
If you feel that this action was inappropriate,
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #4 from vice...@gmail.com ---
Hi! Yes, it is reproducible.
Each time TRIM is enabled via the UDEV rule and the FS mounted with
the discard option, the issue is triggered at the very first write attempt.
Before mounting fsck.f2fs was
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #5 from vice...@gmail.com ---
Created attachment 278227
--> https://bugzilla.kernel.org/attachment.cgi?id=278227=edit
fsck.f2fs
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #6 from vice...@gmail.com ---
Hi, just found that the issue is also reproducible when mounted
with the "nodiscard" option, enabling TRIM via UDEV is enouth.
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #7 from Chao Yu (c...@kernel.org) ---
Created attachment 278233
--> https://bugzilla.kernel.org/attachment.cgi?id=278233=edit
add some log
Can you apply this patch attached and reproduce this bug again?
--
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=200635
Stathis Maneas (sman...@cs.toronto.edu) changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #6 from Stathis Maneas (sman...@cs.toronto.edu) ---
Created attachment 278335
--> https://bugzilla.kernel.org/attachment.cgi?id=278335=edit
Device Mapper Module - Makefile
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #5 from Stathis Maneas (sman...@cs.toronto.edu) ---
Created attachment 278333
--> https://bugzilla.kernel.org/attachment.cgi?id=278333=edit
Device Mapper Module (Injector) - Header File
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #4 from Stathis Maneas (sman...@cs.toronto.edu) ---
Created attachment 278331
--> https://bugzilla.kernel.org/attachment.cgi?id=278331=edit
Device Mapper Module (Injector)
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #7 from Stathis Maneas (sman...@cs.toronto.edu) ---
Please find attached the required files to reproduce the error. Start with the
Makefile to compile and install the module into your kernel.
Assuming the underlying device is
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #8 from Stathis Maneas (sman...@cs.toronto.edu) ---
Created attachment 278337
--> https://bugzilla.kernel.org/attachment.cgi?id=278337=edit
Simple C file that updates the permissions of a file.
--
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=200635
--- Comment #8 from Chao Yu (c...@kernel.org) ---
(In reply to Stathis Maneas from comment #7)
> I can verify that the latter patch is able to resolved the error and thus, I
> am marking the issue as resolved.
>
> Thanks a lot!
You're welcome,
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #16 from vice...@gmail.com ---
Hi,
thank you for being that fast!
I have tried it against v4.19-rc2
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=57361846b52bc686112da6ca5368d11210796804
but it does
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #17 from Chao Yu (c...@kernel.org) ---
Updated in below git link, :)
https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/log/?h=f2fs-dev
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=200951
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #3 from Chao Yu (c...@kernel.org) ---
Alright, can you please provider the complete testcase including error
injection script for me? I'd like to reproduce in my environment.
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=200951
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #17 from Chao Yu (c...@kernel.org) ---
(In reply to Stathis Maneas from comment #16)
> I am sorry for the delay! I can definitely help by adding the aforementioned
> statements!
>
> After adding them and observing the output of
https://bugzilla.kernel.org/show_bug.cgi?id=201555
Bug ID: 201555
Summary: [f2fs] Processes freezing periodically with f2fs root
Product: File System
Version: 2.5
Kernel Version: 4.14 - 4.19 (at least)
Hardware: All
OS:
https://bugzilla.kernel.org/show_bug.cgi?id=201555
--- Comment #4 from Pierpaolo Valerio (gonds...@techgeek.co.in) ---
Ok, I've compiled your dev branch and I'll report back in a few days (or
earlier if the PC freezes again). Thanks!
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=201555
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=201555
--- Comment #3 from Pierpaolo Valerio (gonds...@techgeek.co.in) ---
Created attachment 279271
--> https://bugzilla.kernel.org/attachment.cgi?id=279271=edit
dmesg on 4.14 kernel (but it's the same on newer versions)
--
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=201555
--- Comment #2 from Pierpaolo Valerio (gonds...@techgeek.co.in) ---
I'll try the dev branch as soon as I get the time to do it. I can attach the
full dmesg I got a few days ago for the time being.
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=201555
--- Comment #5 from Pierpaolo Valerio (gonds...@techgeek.co.in) ---
So, my office PC is still up after more than 5 days, so I'm assuming the
problem is either solved or greatly reduced.
When can I expect to see the changes merged? Will it be in a
https://bugzilla.kernel.org/show_bug.cgi?id=201555
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #6 from
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #16 from Stathis Maneas (sman...@cs.toronto.edu) ---
I am sorry for the delay! I can definitely help by adding the aforementioned
statements!
After adding them and observing the output of dmesg, I can observe that only
the second
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #15 from Chao Yu (c...@kernel.org) ---
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 71f5953..1b5d391 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -114,6 +114,11 @@ static void f2fs_write_end_io(struct bio *bio)
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #13 from Chao Yu (c...@kernel.org) ---
(In reply to vicencb from comment #12)
> As stated in the bug description, there is an udev rule to set
Sorry, I missed this one... :(
> the provisioning_mode attribute to unmap. When searching
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #14 from vice...@gmail.com ---
This could explain why it fails on aarch64 but works on x86_64.
When this is tested on aarch64, the f2fs is the root FS, and the udev
rule is applied after mount because it is stored in the filesystemm
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #12 from vice...@gmail.com ---
As stated in the bug description, there is an udev rule to set
the provisioning_mode attribute to unmap. When searching for
this attribute name, i found this:
drivers/scsi/sd.c:749
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #11 from Chao Yu (c...@kernel.org) ---
Actually, the problem here is during mount(), both blk_queue_discard(q) and
f2fs_sb_has_blkzoned(sbi) return false, so f2fs will skip allocating memory for
se->discard_map.
static inline bool
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #8 from vice...@gmail.com ---
Created attachment 278241
--> https://bugzilla.kernel.org/attachment.cgi?id=278241=edit
log results
Hi, here are the results asked for.
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #9 from vice...@gmail.com ---
Created attachment 278243
--> https://bugzilla.kernel.org/attachment.cgi?id=278243=edit
add some log (bis)
Hi, added a few more printk for extra verbosity.
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #10 from vice...@gmail.com ---
Created attachment 278245
--> https://bugzilla.kernel.org/attachment.cgi?id=278245=edit
log results (bis)
The results of the previous patch.
--
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #15 from Chao Yu (c...@kernel.org) ---
I've sent one patch for this issue, just cc your email, also you can find the
patch in below link[1], can you please try this patch to check whether it can
fix this issue?
[1]
https://bugzilla.kernel.org/show_bug.cgi?id=200465
--- Comment #4 from Wen Xu (wen...@gatech.edu) ---
(In reply to Chao Yu from comment #3)
> Steve,
>
> I figure out that patch to solve issue which I encounter with image attached
> by Wen Xu, the bug can be triggered with below scripts:
> -
https://bugzilla.kernel.org/show_bug.cgi?id=200773
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||datadan...@163.com
---
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #9 from Chao Yu (c...@kernel.org) ---
Sorry for putting it off, I just struggled to fix quota things in these days,
let me try to reproduce this issue.
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=200465
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|ASSIGNED|NEEDINFO
--- Comment #5 from
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #10 from Chao Yu (c...@kernel.org) ---
(In reply to Stathis Maneas from comment #7)
> Please find attached the required files to reproduce the error. Start with
> the Makefile to compile and install the module into your kernel.
>
>
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #11 from Stathis Maneas (sman...@cs.toronto.edu) ---
Considering the fact that the operation modifies the entry's inode and that
fsync is invoked at the end of the program so that all modifications persist,
then a new inode will
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #13 from Stathis Maneas (sman...@cs.toronto.edu) ---
Indeed, I can tell what is the block address in which the updated inode is
going to be stored using both dump.f2fs and the output of the SSA blocks.
Then, the file system gets
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #14 from Chao Yu (c...@kernel.org) ---
(In reply to Stathis Maneas from comment #13)
> Indeed, I can tell what is the block address in which the updated inode is
> going to be stored using both dump.f2fs and the output of the SSA
https://bugzilla.kernel.org/show_bug.cgi?id=201911
Jaegeuk Kim (jaeg...@kernel.org) changed:
What|Removed |Added
CC||jaeg...@kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=201911
--- Comment #2 from liushuanglin (liu_shuang_...@163.com) ---
Hi, Yu,
Tried two patches you mentioned, still reproduced this issue.
will try latest f2fs codes.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=201911
Bug ID: 201911
Summary: High frequency of gc cause application database
corrupt
Product: File System
Version: 2.5
Kernel Version: 4.9
Hardware: ARM
OS:
https://bugzilla.kernel.org/show_bug.cgi?id=201911
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=200465
--- Comment #3 from Chao Yu (c...@kernel.org) ---
Steve,
I figure out that patch to solve issue which I encounter with image attached by
Wen Xu, the bug can be triggered with below scripts:
- mount image /mnt/f2fs/
- cd /mnt/f2fs/foo/bar/
- ls
https://bugzilla.kernel.org/show_bug.cgi?id=200465
Steve Beattie (sbeat...@ubuntu.com) changed:
What|Removed |Added
CC||sbeat...@ubuntu.com
https://bugzilla.kernel.org/show_bug.cgi?id=202989
--- Comment #8 from Lianjun Huang (hlian...@gmail.com) ---
(In reply to Chao Yu from comment #7)
> I've changed this issue's title to indicate it is from private code repo.
It is OK.
>
> Could you add to Cc below email address of qualcomm's
https://bugzilla.kernel.org/show_bug.cgi?id=202989
--- Comment #9 from yuch...@huawei.com ---
On 2019/3/25 11:38, bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=202989
>
> --- Comment #8 from Lianjun Huang (hlian...@gmail.com) ---
> (In reply to Chao Yu
https://bugzilla.kernel.org/show_bug.cgi?id=203163
Bug ID: 203163
Summary: RIP: 0010:update_sit_entry+0x50/0x420 when mounting
crafted image
Product: File System
Version: 2.5
Kernel Version: 5.0.0
Hardware: All
https://bugzilla.kernel.org/show_bug.cgi?id=203169
Bug ID: 203169
Summary: at fs/f2fs/checkpoint.c:160 f2fs_is_valid_blkaddr
Product: File System
Version: 2.5
Kernel Version: 5.0.0
Hardware: All
OS: Linux
https://bugzilla.kernel.org/show_bug.cgi?id=203169
Jungyeon (jungy...@gatech.edu) changed:
What|Removed |Added
Summary|at fs/f2fs/checkpoint.c:160 |crash at
https://bugzilla.kernel.org/show_bug.cgi?id=203171
Bug ID: 203171
Summary: PF error: at __remove_dirty_segment+0x61/0xd0
Product: File System
Version: 2.5
Kernel Version: 5.0.0
Hardware: All
OS: Linux
Tree:
https://bugzilla.kernel.org/show_bug.cgi?id=203165
--- Comment #2 from Jungyeon (jungy...@gatech.edu) ---
Created attachment 282151
--> https://bugzilla.kernel.org/attachment.cgi?id=282151=edit
poc_02.c
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=203165
--- Comment #1 from Jungyeon (jungy...@gatech.edu) ---
Created attachment 282149
--> https://bugzilla.kernel.org/attachment.cgi?id=282149=edit
The (compressed) crafted image which causes crash
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=203169
--- Comment #1 from Jungyeon (jungy...@gatech.edu) ---
- Overview
When mounting attached crafted image and making an empty file, I got this
error.
- Produces
mkdir test
mount -t f2fs tmp.img test
cd test
sudo touch t
dmesg
--
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=203169
--- Comment #2 from Jungyeon (jungy...@gatech.edu) ---
Created attachment 282155
--> https://bugzilla.kernel.org/attachment.cgi?id=282155=edit
The (compressed) crafted image which causes crash
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=203167
Bug ID: 203167
Summary: Kernel page fault with update_sit_entry+0x113/0x420
Product: File System
Version: 2.5
Kernel Version: 5.0.0
Hardware: All
OS: Linux
https://bugzilla.kernel.org/show_bug.cgi?id=203165
Bug ID: 203165
Summary: Kernel panic - not syncing: corrupted stack end
detected inside scheduler
Product: File System
Version: 2.5
Kernel Version: 5.0.0
Hardware: All
https://bugzilla.kernel.org/show_bug.cgi?id=203169
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=202989
--- Comment #6 from Chao Yu (c...@kernel.org) ---
> I would like to clarify that kernel panic are from two different machines.
> And both new_blkaddr and old_blkaddr of fio are 0x.
Okay, so that we need to add log to track block address
https://bugzilla.kernel.org/show_bug.cgi?id=202989
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Summary|kernel panic during F2FS GC |[MSM-4.14] kernel panic
https://bugzilla.kernel.org/show_bug.cgi?id=202637
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=202637
--- Comment #2 from Seulbae Kim (seul...@gatech.edu) ---
Thank you for quick response Chao Yu!
I tested your patch by applying it on kernel v5.0.0-rc7, and confirmed that the
reported bug is fixed.
(In reply to Chao Yu from comment #1)
>
https://bugzilla.kernel.org/show_bug.cgi?id=202637
--- Comment #3 from Chao Yu (c...@kernel.org) ---
Thanks for the quick test. :)
I've also sent a patch to simulate your testcase for fstest suit, you can find
it in below link:
https://bugzilla.kernel.org/show_bug.cgi?id=202709
Bug ID: 202709
Summary: Crafted image causes buffer overflow in
read_inline_xattr
Product: File System
Version: 2.5
Kernel Version: 4.20
Hardware: All
1 - 100 of 674 matches
Mail list logo
