https://bugzilla.kernel.org/show_bug.cgi?id=210765
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=210745
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |NEEDINFO
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=210765
junkmailnotr...@yahoo.com changed:
What|Removed |Added
CC||junkmailnotr...@yahoo.com
---
https://bugzilla.kernel.org/show_bug.cgi?id=210795
Bug ID: 210795
Summary: fsck.f2fs - 1.14.0 - error when not /dev/vgXX/lvYYY
path provided - [ASSERT] (init_sb_info:1017)
!strcmp((char *)sb->devs[i].path, (char
*)c
https://bugzilla.kernel.org/show_bug.cgi?id=210797
Bug ID: 210797
Summary: resize.f2fs over 2 (LVM) disks corrupts whole
filesystem
Product: File System
Version: 2.5
Kernel Version: 5.9.15
Hardware: All
https://bugzilla.kernel.org/show_bug.cgi?id=210795
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=210797
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=210745
--- Comment #2 from Zhiguo.Niu (zhiguo@unisoc.com) ---
(In reply to Chao Yu from comment #1)
> Hi,
>
> I checked the code of 4.14.193, I don't have any clue about why this can
> happen,
> and I don't remember that there is such corruption con
https://bugzilla.kernel.org/show_bug.cgi?id=210745
--- Comment #3 from Chao Yu (c...@kernel.org) ---
nm_i->nat_list_lock was introduced in 4.19, are you sure your codebase is
4.14.193?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the ass
https://bugzilla.kernel.org/show_bug.cgi?id=210745
--- Comment #4 from Chao Yu (c...@kernel.org) ---
(In reply to Zhiguo.Niu from comment #2)
> hi Chao,
>
> Thanks for your reply, I have checked my codebase, there is no any other
> private patches in current version.
>
> I find that local varia
https://bugzilla.kernel.org/show_bug.cgi?id=210825
Bug ID: 210825
Summary: Data corruption occurs with heavy I/O on f2fs
filesystems with kernel 5.10
Product: File System
Version: 2.5
Kernel Version: 5.10.1
Hardware: Al
https://bugzilla.kernel.org/show_bug.cgi?id=210825
nvaert1986 (nvaert1...@hotmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Re
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
--- 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 *)page_addre
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=200635
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
Ass
https://bugzilla.kernel.org/show_bug.cgi?id=200871
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
Ass
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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e494c
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=200635
Stathis Maneas (sman...@cs.toronto.edu) changed:
What|Removed |Added
Status|RESOLVED|REOPENED
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=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=200185
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=200423
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=200171
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
Comp
https://bugzilla.kernel.org/show_bug.cgi?id=200167
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
Comp
https://bugzilla.kernel.org/show_bug.cgi?id=200175
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
Comp
https://bugzilla.kernel.org/show_bug.cgi?id=200179
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
Comp
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=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 case
https://bugzilla.kernel.org/show_bug.cgi?id=200173
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
Comp
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=200871
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from
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 th
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 introduc
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&action=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=200951
--- Comment #2 from vice...@gmail.com ---
Created attachment 278131
--> https://bugzilla.kernel.org/attachment.cgi?id=278131&action=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=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/
I
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 t
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=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 su
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&action=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 the
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&action=edit
add some log
Can you apply this patch attached and reproduce this bug again?
--
You are receiving
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&action=edit
log results
Hi, here are the results asked for.
--
You are receiving this mail because:
You are watching
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&action=edit
add some log (bis)
Hi, added a few more printk for extra verbosity.
--
You are receiving this mail becaus
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&action=edit
log results (bis)
The results of the previous patch.
--
You are receiving this mail because:
You are wat
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 f2
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
blk_queue_max_discard
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 it
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://sourceforge
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 not
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=200635
Stathis Maneas (sman...@cs.toronto.edu) changed:
What|Removed |Added
Status|REOPENED|RESOLVED
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&action=edit
Device Mapper Module (Injector)
--
You are receiving this mail because:
You are watc
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&action=edit
Device Mapper Module (Injector) - Header File
--
You are receiving this mail because
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&action=edit
Device Mapper Module - Makefile
--
You are receiving this mail because:
You are watc
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 /dev/vdb
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&action=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, i
https://bugzilla.kernel.org/show_bug.cgi?id=200951
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|-
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=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 -l
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:
> - mount
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=200773
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||datadan...@163.com
--- Commen
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 bug.
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.
>
> As
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 eventu
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #12 from Chao Yu (c...@kernel.org) ---
(In reply to Stathis Maneas from comment #7)
> - The block number (on disk) that will accommodate the newly updated inode
> (after its mode has changed). In my case, this block number is equal to
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 initi
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 block
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=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 stat
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 dmesg,
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: Lin
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 #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 #3 from Pierpaolo Valerio (gonds...@techgeek.co.in) ---
Created attachment 279271
--> https://bugzilla.kernel.org/attachment.cgi?id=279271&action=edit
dmesg on 4.14 kernel (but it's the same on newer versions)
--
You are receiving
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 a
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=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=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
Jaegeuk Kim (jaeg...@kernel.org) changed:
What|Removed |Added
CC||jaeg...@kernel.org
---
https://bugzilla.kernel.org/show_bug.cgi?id=202495
Bug ID: 202495
Summary: oops in fs/f2fs/checkpoint.c:150 f2fs_is_valid_blkaddr
Product: File System
Version: 2.5
Kernel Version: 4.14.97
Hardware: ARM
OS: Linux
https://bugzilla.kernel.org/show_bug.cgi?id=202495
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
CC||c...@kernel.org
--- Comment #
https://bugzilla.kernel.org/show_bug.cgi?id=202495
--- Comment #2 from JWalker (jw7...@gmail.com) ---
Hi Chao,
The kernal code was taken from the raspberry pi git repo, and then the
incremental patches applied.
Yes, fsck has been applied. Please see below the output of the both volumes.
Please
https://bugzilla.kernel.org/show_bug.cgi?id=202495
--- Comment #3 from Chao Yu (c...@kernel.org) ---
(In reply to JWalker from comment #2)
> Hi Chao,
>
> The kernal code was taken from the raspberry pi git repo, and then the
> incremental patches applied.
What patches do you applied? some fixing
https://bugzilla.kernel.org/show_bug.cgi?id=202495
--- Comment #4 from JWalker (jw7...@gmail.com) ---
Hi Chao,
I’ve applied all incremental patches up to, including 4.14.101. I can also
confirm that my build is a %100 match between the .xz file on kernel.org (
with respect to fs/* ).
Yes , totally
https://bugzilla.kernel.org/show_bug.cgi?id=202637
Bug ID: 202637
Summary: Chmod'ed directory permission is not persisted with
fsync
Product: File System
Version: 2.5
Kernel Version: v5.0.0-rc7 (latest)
Hardware: All
https://bugzilla.kernel.org/show_bug.cgi?id=202637
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
301 - 400 of 743 matches
Mail list logo
