[f2fs-dev] [Bug 204043] F2fs kernel BUG at fs/f2fs/data.c:317!

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204043 --- Comment #2 from midwinter1...@gmail.com --- (In reply to Chao Yu from comment #1) > Could you help to add below diff to check debug info? > > diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c > index bc5cea27b512..333285cb14c5 100644 > ---

[f2fs-dev] [Bug 203223] hangs on running program after mounting a crafted image

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203223 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 203233] kernel BUG at fs/f2fs/segment.c:2102!

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203233 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[f2fs-dev] [Bug 203345] page fault and hang on mounting crafted image and running program

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203345 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 203163] RIP: 0010:update_sit_entry+0x50/0x420 when mounting crafted image

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203163 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 203165] Kernel panic - not syncing: corrupted stack end detected inside scheduler

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203165 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 203343] page fault and hang on umounting

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203343 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[f2fs-dev] [Bug 203235] kernel BUG at fs/f2fs/segment.c:2131! and hangs on sync

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203235 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 203231] kernel BUG at fs/f2fs/segment.c:2079! and hangs on sync

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203231 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 203215] failure at fs/f2fs/f2fs.h:2809/verify_blkaddr()!

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203215 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[f2fs-dev] [Bug 203171] PF error: at __remove_dirty_segment+0x61/0xd0

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203171 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 203341] Kernel read fault when mounting a crafted image and running program

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203341 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 203167] Kernel page fault with update_sit_entry+0x113/0x420

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203167 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[f2fs-dev] [Bug 203241] kernel BUG at fs/f2fs/segment.c:3222! and hangs on sync

2019-07-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203241 Jungyeon (jungy...@gatech.edu) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 203861] Division by zero error in fsck.f2fs when fixing a corrupted image

2019-07-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203861 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[f2fs-dev] [Bug 203861] Division by zero error in fsck.f2fs when fixing a corrupted image

2019-07-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203861 --- Comment #2 from Seulbae Kim (seul...@gatech.edu) --- No problem. I checked that the bug is fixed through the patch. Thank you! -- You are receiving this mail because: You are watching the assignee of the bug.

[f2fs-dev] [Bug 203197] kernel read fault at __is_cp_guaranteed

2019-04-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203197 Chao Yu (c...@kernel.org) changed: What|Removed |Added CC||c...@kernel.org --- Comment

[f2fs-dev] [Bug 203197] New: kernel read fault at __is_cp_guaranteed

2019-04-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203197 Bug ID: 203197 Summary: kernel read fault at __is_cp_guaranteed Product: File System Version: 2.5 Kernel Version: 5.0.0 Hardware: All OS: Linux Tree:

[f2fs-dev] [Bug 203167] Kernel page fault with update_sit_entry+0x113/0x420

2019-04-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203167 --- Comment #2 from Jungyeon (jungy...@gatech.edu) --- I checked with CONFIG_F2FS_CHECK_FS option on, and it shows that f2fs mount errors not crashing. However, CONFIG_F2FS_CHECK_FS is not enabled by default, and I guess that there is a high

[f2fs-dev] [Bug 204135] F2FS: BUG: KASAN: null-ptr-deref in mempool_alloc+0xd8/0x2e0

2019-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204135 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[f2fs-dev] [Bug 204043] F2fs kernel BUG at fs/f2fs/data.c:317!

2019-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204043 --- Comment #4 from Chao Yu (c...@kernel.org) --- Sorry, previous version is broken... I've updated them. https://lore.kernel.org/linux-f2fs-devel/20190712085542.4068-1-yuch...@huawei.com/T/#u -- You are receiving this mail because: You are

[f2fs-dev] [Bug 204135] F2FS: BUG: KASAN: null-ptr-deref in mempool_alloc+0xd8/0x2e0

2019-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204135 --- Comment #3 from Chao Yu (c...@kernel.org) --- F2FS_IO_ALIGNED() was defined in last patch for your previous issue... so, should apply them before this patch. Could you change to last code in dev branch in Jaegeuk's git repo.

[f2fs-dev] [Bug 204043] F2fs kernel BUG at fs/f2fs/data.c:317!

2019-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204043 Chao Yu (c...@kernel.org) changed: What|Removed |Added Comment #6 is|1 |0 private|

[f2fs-dev] [Bug 202495] oops in fs/f2fs/checkpoint.c:150 f2fs_is_valid_blkaddr

2019-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202495 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 204043] F2fs kernel BUG at fs/f2fs/data.c:317!

2019-07-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204043 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[f2fs-dev] [Bug 204135] F2FS: BUG: KASAN: null-ptr-deref in mempool_alloc+0xd8/0x2e0

2019-07-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204135 --- Comment #6 from midwinter1...@gmail.com --- (In reply to Chao Yu from comment #5) > Sorry, I meant I made the two fix patches based Jaegeuk's git repo, however > Jaegeuk hasn't merge the two patches in his branch. > > So you can do the merge

[f2fs-dev] [Bug 204135] F2FS: BUG: KASAN: null-ptr-deref in mempool_alloc+0xd8/0x2e0

2019-07-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204135 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[f2fs-dev] [Bug 204043] F2fs kernel BUG at fs/f2fs/data.c:317!

2019-07-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204043 --- Comment #10 from midwinter1...@gmail.com --- (In reply to Chao Yu from comment #8) > This bug was reported by you in another track... > > So could you confirm the issue in this track again? Sorry! I forgot that bug. I have tested the patch

[f2fs-dev] [Bug 204137] F2FS: kernel BUG at fs/f2fs/segment.c:2375!

2019-08-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204137 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[f2fs-dev] [Bug 202495] oops in fs/f2fs/checkpoint.c:150 f2fs_is_valid_blkaddr

2019-07-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202495 --- Comment #7 from phiber2...@gmx.de --- (In reply to Chao Yu from comment #6) > Was fixed with a backported patch ("f2fs: fix to skip verifying block > address for non-regular inode") Maybe my mistake, but I can't find the backported patch in

[f2fs-dev] [Bug 202495] oops in fs/f2fs/checkpoint.c:150 f2fs_is_valid_blkaddr

2019-07-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202495 --- Comment #8 from Chao Yu (c...@kernel.org) --- It's here, it should be merged in AOSP as well. :) https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-stable.git/commit/?h=linux-4.14.y=3cc9792fa1ea67bbfdaee28737e37f9045976b76 -- You

[f2fs-dev] [Bug 204193] BUG: KASAN: null-ptr-deref in f2fs_write_end_io+0x215/0x650

2019-07-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204193 --- Comment #2 from midwinter1...@gmail.com --- (In reply to Chao Yu from comment #1) > How to reproduce this, remount to change io_bits option? It's not triggered by remount, the following script manifests it (note that this bug does not occur

[f2fs-dev] [Bug 204193] BUG: KASAN: null-ptr-deref in f2fs_write_end_io+0x215/0x650

2019-07-18 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204193 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #3 from

[f2fs-dev] [Bug 66631] F2FS-fs reports error for valid mount options

2019-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=66631 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |RESOLVED CC|

[f2fs-dev] [Bug 200219] Buffer overrun when reading inline data in f2fs

2019-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=200219 Chao Yu (c...@kernel.org) changed: What|Removed |Added CC||c...@kernel.org

[f2fs-dev] [Bug 104211] segfault / heap out of bounds read in fsck.f2fs

2019-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=104211 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |RESOLVED CC|

[f2fs-dev] [Bug 204193] New: BUG: KASAN: null-ptr-deref in f2fs_write_end_io+0x215/0x650

2019-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204193 Bug ID: 204193 Summary: BUG: KASAN: null-ptr-deref in f2fs_write_end_io+0x215/0x650 Product: File System Version: 2.5 Kernel Version: 5.1.3 Hardware: All

[f2fs-dev] [Bug 204193] BUG: KASAN: null-ptr-deref in f2fs_write_end_io+0x215/0x650

2019-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204193 Chao Yu (c...@kernel.org) changed: What|Removed |Added CC||c...@kernel.org --- Comment

[f2fs-dev] [Bug 204197] New: F2FS: kernel BUG at fs/f2fs/inode.c:722!

2019-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204197 Bug ID: 204197 Summary: F2FS: kernel BUG at fs/f2fs/inode.c:722! Product: File System Version: 2.5 Kernel Version: 5.1.3 Hardware: All OS: Linux Tree:

[f2fs-dev] [Bug 204043] F2fs kernel BUG at fs/f2fs/data.c:317!

2019-07-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204043 --- Comment #7 from midwinter1...@gmail.com --- (In reply to Chao Yu from comment #6) > You mean it failed when you apply those patches to kernel 5.1.3? > > I made patches based on last dev branch below: > >

[f2fs-dev] [Bug 204193] BUG: KASAN: null-ptr-deref in f2fs_write_end_io+0x215/0x650

2019-07-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204193 --- Comment #4 from midwinter1...@gmail.com --- (In reply to Chao Yu from comment #3) > Thanks, I can reproduce it now. > > I've made a patch for this issue, could you verify it? > >

[f2fs-dev] [Bug 204135] F2FS: BUG: KASAN: null-ptr-deref in mempool_alloc+0xd8/0x2e0

2019-07-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204135 --- Comment #4 from midwinter1...@gmail.com --- (In reply to Chao Yu from comment #3) > F2FS_IO_ALIGNED() was defined in last patch for your previous issue... so, > should apply them before this patch. > > Could you change to last code in dev

[f2fs-dev] [Bug 204193] BUG: KASAN: null-ptr-deref in f2fs_write_end_io+0x215/0x650

2019-07-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204193 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[f2fs-dev] [Bug 204043] F2fs kernel BUG at fs/f2fs/data.c:317!

2019-07-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204043 --- Comment #8 from Chao Yu (c...@kernel.org) --- This bug was reported by you in another track... So could you confirm the issue in this track again? -- You are receiving this mail because: You are watching the assignee of the bug.

[f2fs-dev] [Bug 204135] F2FS: BUG: KASAN: null-ptr-deref in mempool_alloc+0xd8/0x2e0

2019-07-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204135 --- Comment #5 from Chao Yu (c...@kernel.org) --- Sorry, I meant I made the two fix patches based Jaegeuk's git repo, however Jaegeuk hasn't merge the two patches in his branch. So you can do the merge by yourself, or you can use below codes in

[f2fs-dev] [Bug 204043] F2fs kernel BUG at fs/f2fs/data.c:317!

2019-07-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204043 --- Comment #9 from Chao Yu (c...@kernel.org) --- BTW, to avoid panic in new_curseg(), you'd better to expand image size. -- You are receiving this mail because: You are watching the assignee of the bug.

[f2fs-dev] [Bug 204197] F2FS: kernel BUG at fs/f2fs/inode.c:722!

2019-07-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204197 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[f2fs-dev] [Bug 205181] kernel panic when accessing btrfs root device with f2fs in kernel

2019-10-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205181 --- Comment #4 from Roger (rogan6...@gmail.com) --- Thanks for the quick response 4.19.80 works just fine here :) -- You are receiving this mail because: You are watching the assignee of the bug. ___

[f2fs-dev] [Bug 205203] New: ram_thresh default (DEF_RAM_THRESHOLD) is wrong (outdated) in f2fs document

2019-10-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205203 Bug ID: 205203 Summary: ram_thresh default (DEF_RAM_THRESHOLD) is wrong (outdated) in f2fs document Product: File System Version: 2.5 Kernel Version: all Hardware: All

[f2fs-dev] [Bug 205203] ram_thresh default (DEF_RAM_THRESHOLD) is wrong (outdated) in f2fs document

2019-10-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205203 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[f2fs-dev] [Bug 205181] New: kernel panic when accessing btrfs root device with f2fs in kernel

2019-10-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205181 Bug ID: 205181 Summary: kernel panic when accessing btrfs root device with f2fs in kernel Product: File System Version: 2.5 Kernel Version: 4.19.76-4.19.79 Hardware:

[f2fs-dev] [Bug 205181] kernel panic when accessing btrfs root device with f2fs in kernel

2019-10-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205181 --- Comment #1 from Roger (rogan6...@gmail.com) --- Related linuxquestions.org thread: https://www.linuxquestions.org/questions/slackware-14/the-latest-kernel-release-4175597503/page112.html -- You are receiving this mail because: You are

[f2fs-dev] [Bug 205181] kernel panic when accessing btrfs root device with f2fs in kernel

2019-10-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205181 Andrew Macks (andy...@gmail.com) changed: What|Removed |Added CC||andy...@gmail.com ---

[f2fs-dev] [Bug 205181] kernel panic when accessing btrfs root device with f2fs in kernel

2019-10-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205181 --- Comment #3 from Roger (rogan6...@gmail.com) --- Thanks for the reply. This is a real mess for Slackware since we use "huge" kernels with support for nearly every file system as default installation kernels. This particular flavour often

[f2fs-dev] [Bug 205967] New: [bisected] f2fs compression support breaks build

2019-12-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205967 Bug ID: 205967 Summary: [bisected] f2fs compression support breaks build Product: File System Version: 2.5 Kernel Version: 5.5.0-rc2-next Hardware: All OS: Linux

[f2fs-dev] [Bug 206551] Failed to initialize F2FS segment manager (-117)

2020-02-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206551 --- Comment #5 from Stefan de Konink (ste...@konink.de) --- [1.404552] F2FS-fs (sda4): Found nat_bits in checkpoint [1.638356] F2FS-fs (sda4): Mounted with checkpoint version = 68992090 I don't have the dmesg of the 'recovery' attempts.

[f2fs-dev] [Bug 206551] Failed to initialize F2FS segment manager (-117)

2020-02-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206551 --- Comment #4 from Chao Yu (c...@kernel.org) --- What's your mkfs option and mount option? Can you upload kernel message? maybe we can find clue from it. Thanks, -- You are receiving this mail because: You are watching the assignee of the

[f2fs-dev] [Bug 206551] New: Failed to initialize F2FS segment manager (-117)

2020-02-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206551 Bug ID: 206551 Summary: Failed to initialize F2FS segment manager (-117) Product: File System Version: 2.5 Kernel Version: 5.5.3-gentoo Hardware: x86-64 OS: Linux

[f2fs-dev] [Bug 206551] Failed to initialize F2FS segment manager (-117)

2020-02-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206551 --- Comment #1 from Stefan de Konink (ste...@konink.de) --- Created attachment 287425 --> https://bugzilla.kernel.org/attachment.cgi?id=287425=edit fsck.f2fs result specifically showing SIT bitmap is 0x0. -- You are receiving this mail

[f2fs-dev] [Bug 206551] Failed to initialize F2FS segment manager (-117)

2020-02-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206551 --- Comment #3 from Stefan de Konink (ste...@konink.de) --- My swap partition is at /dev/sda3, as independent of f2fs. -- You are receiving this mail because: You are watching the assignee of the bug.

[f2fs-dev] [Bug 206551] Failed to initialize F2FS segment manager (-117)

2020-02-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206551 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[f2fs-dev] [Bug 206551] Failed to initialize F2FS segment manager (-117)

2020-02-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206551 --- Comment #6 from Chao Yu (c...@kernel.org) --- IIRC, in knew bugs, except swap file feature, large_nat_bitmap feature can also damage f2fs metadata (SIT table) (they are all fixed in mainline), did you enable this feature during mkfs/resize?

[f2fs-dev] [Bug 206057] 5.5.0-rc2-next: f2fs is extremely slow, with ext4 system works well

2020-01-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206057 --- Comment #3 from David Heidelberg (okias) (da...@ixit.cz) --- (also patch didn't helped) -- You are receiving this mail because: You are watching the assignee of the bug. ___ Linux-f2fs-devel

[f2fs-dev] [Bug 206057] 5.5.0-rc2-next: f2fs is extremely slow, with ext4 system works well

2020-01-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206057 --- Comment #4 from Chao Yu (c...@kernel.org) --- Thanks for the help, I've bisected the bad commit ("f2fs: cover f2fs_lock_op in expand_inode_data case"), could you revert it and do the test again? -- You are receiving this mail because: You

[f2fs-dev] [Bug 206057] 5.5.0-rc2-next: f2fs is extremely slow, with ext4 system works well

2020-01-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206057 --- Comment #5 from David Heidelberg (okias) (da...@ixit.cz) --- sadly, still same output. Also not sure why, sudo -i freezes and cannot be stopped by CTRL-C. -- You are receiving this mail because: You are watching the assignee of the bug.

[f2fs-dev] [Bug 205967] [bisected] f2fs compression support breaks build

2020-01-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205967 David Heidelberg (okias) (da...@ixit.cz) changed: What|Removed |Added Status|NEW |RESOLVED

[f2fs-dev] [Bug 206057] New: 5.5.0: f2fs is extremely slow, with ext4 system works well

2020-01-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206057 Bug ID: 206057 Summary: 5.5.0: f2fs is extremely slow, with ext4 system works well Product: File System Version: 2.5 Kernel Version: 5.5.0-rc2-next Hardware: All

[f2fs-dev] [Bug 206057] 5.5.0-rc2-next: f2fs is extremely slow, with ext4 system works well

2020-01-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206057 Chao Yu (c...@kernel.org) changed: What|Removed |Added CC||c...@kernel.org --- Comment

[f2fs-dev] [Bug 206057] 5.5.0-rc2-next: f2fs is extremely slow, with ext4 system works well

2020-01-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206057 --- Comment #2 from David Heidelberg (okias) (da...@ixit.cz) --- I'm not sure I can try bisect (since using custom patches to run device), anyway if it helps, F2FS filesystem has been created by TWRP (kernel 3.1). I'll try get complete f2fs

[f2fs-dev] [Bug 205203] ram_thresh default (DEF_RAM_THRESHOLD) is wrong (outdated) in f2fs document

2019-12-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205203 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[f2fs-dev] [Bug 206057] 5.5.0-rc2-next: f2fs is extremely slow, with ext4 system works well

2020-04-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206057 Balazs Vinarz (viniba...@gmail.com) changed: What|Removed |Added CC||viniba...@gmail.com

[f2fs-dev] [Bug 206057] 5.5.0-rc2-next: f2fs is extremely slow, with ext4 system works well

2020-04-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206057 --- Comment #9 from Jaegeuk Kim (jaeg...@kernel.org) --- (In reply to Balazs Vinarz from comment #8) > Hello there, > > as a 32bit ARM user, I'm also affected. > Will this fix be in 5.7? > > Regards Yes, it was merged in 5.7-rc1. -- You are

[f2fs-dev] [Bug 206057] 5.5.0-rc2-next: f2fs is extremely slow, with ext4 system works well

2020-03-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206057 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #7 from

[f2fs-dev] [Bug 208955] The file system accidentally stops working

2020-09-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208955 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |NEEDINFO CC|

[f2fs-dev] [Bug 208955] New: The file system accidentally stops working

2020-08-18 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208955 Bug ID: 208955 Summary: The file system accidentally stops working Product: File System Version: 2.5 Kernel Version: 5.8.1-zen1-1-zen Hardware: x86-64 OS: Linux

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 --- Comment #5 from Zhiguo.Niu (zhiguo@unisoc.com) --- (In reply to Jaegeuk Kim from comment #1) > Thank you for the report. > > I think this is valid point that we need to fix. > I'm testing a RFC patch like this. Thanks. > > ---

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 --- Comment #4 from Chao Yu (c...@kernel.org) --- Passed, we should ask Eric to retest in his enviornment, to make sure there is actually no regression. -- You are receiving this mail because: You are watching the assignee of the bug.

[f2fs-dev] [Bug 208325] f2fs inconsistent node block

2020-06-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208325 --- Comment #3 from Chao Yu (c...@kernel.org) --- (In reply to zKqri0 from comment #2) > Mount options are "/dev/sda2 on / type f2fs > (rw,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr, >

[f2fs-dev] [Bug 208565] New: There may be dead lock for cp_rwsem during checkpoint

2020-07-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 Bug ID: 208565 Summary: There may be dead lock for cp_rwsem during checkpoint Product: File System Version: 2.5 Kernel Version: 4.14.181 Hardware: All OS: Linux

[f2fs-dev] [Bug 208325] f2fs inconsistent node block

2020-07-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208325 --- Comment #6 from zkq...@gmail.com --- (In reply to Chao Yu from comment #5) > (In reply to zKqri0 from comment #4) > > >[print_node_info: 271] Node ID [0x203a7962:540703074] is direct node or > > >>indirect node. > > >[0]

[f2fs-dev] [Bug 208325] f2fs inconsistent node block

2020-07-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208325 --- Comment #5 from Chao Yu (c...@kernel.org) --- (In reply to zKqri0 from comment #4) > >[print_node_info: 271] Node ID [0x203a7962:540703074] is direct node or > >>indirect node. > >[0][0x5452202c : 1414668332] > >[1]

[f2fs-dev] [Bug 208325] f2fs inconsistent node block

2020-06-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208325 --- Comment #4 from zkq...@gmail.com --- (In reply to Chao Yu from comment #3) > (In reply to zKqri0 from comment #2) > > Mount options are "/dev/sda2 on / type f2fs > > (rw,relatime,lazytime,background_gc=on,discard,no_heap,user_xattr, > >

[f2fs-dev] [Bug 208325] New: f2fs inconsistent node block

2020-06-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208325 Bug ID: 208325 Summary: f2fs inconsistent node block Product: File System Version: 2.5 Kernel Version: 5.7.2-arch1-1 Hardware: All OS: Linux Tree: Mainline

[f2fs-dev] [Bug 208325] f2fs inconsistent node block

2020-06-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208325 --- Comment #2 from zkq...@gmail.com --- (In reply to Chao Yu from comment #1) > Hi, thanks for the report. > > What's you mkfs/mount option? > > I've no idea whether this is a f2fs bug or not, as you said device can be > trusted, so almostly

[f2fs-dev] [Bug 208325] f2fs inconsistent node block

2020-06-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208325 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |NEEDINFO CC|

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 --- Comment #12 from Jaegeuk Kim (jaeg...@kernel.org) --- It'll be called by node_inode->writepages() -> f2fs_write_node_pages(), which should be done by flusher in vfs. -- You are receiving this mail because: You are watching the assignee of

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 --- Comment #6 from Zhiguo.Niu (zhiguo@unisoc.com) --- Hi Jaegeuk Kim Could I merge this patch in my code for fixing the deadlock issue? thanks! -- You are receiving this mail because: You are watching the assignee of the bug.

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 Jaegeuk Kim (jaeg...@kernel.org) changed: What|Removed |Added CC||jaeg...@kernel.org

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 --- Comment #7 from yuch...@huawei.com --- On 2020/7/17 1:15, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208565 > > Jaegeuk Kim (jaeg...@kernel.org) changed: > > What|Removed

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 --- Comment #9 from yuch...@huawei.com --- On 2020/7/24 11:21, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208565 > > --- Comment #8 from Jaegeuk Kim (jaeg...@kernel.org) --- > Chao, why do we need to

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 --- Comment #8 from Jaegeuk Kim (jaeg...@kernel.org) --- Chao, why do we need to revert that patch? Zhiguo, You can see the patch here.

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 --- Comment #10 from Jaegeuk Kim (jaeg...@kernel.org) --- if we revert it, we're not going to call f2fs_flush_inline_data() in checkpoint path, which actually fixes generic/204? -- You are receiving this mail because: You are watching the

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 --- Comment #11 from Zhiguo.Niu (zhiguo@unisoc.com) --- (In reply to Jaegeuk Kim from comment #10) > if we revert it, we're not going to call f2fs_flush_inline_data() in > checkpoint path, which actually fixes generic/204? Hi Jaeqeuk Kim, I

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[f2fs-dev] [Bug 208565] There may be dead lock for cp_rwsem during checkpoint

2020-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=208565 --- Comment #3 from Jaegeuk Kim (jaeg...@kernel.org) --- That passed. could you check your side? -- You are receiving this mail because: You are watching the assignee of the bug. ___ Linux-f2fs-devel

[f2fs-dev] [Bug 210765] New: F2FS causes access invalid blkaddr

2020-12-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210765 Bug ID: 210765 Summary: F2FS causes access invalid blkaddr Product: File System Version: 2.5 Kernel Version: 5.10.1 Hardware: x86-64 OS: Linux Tree: Mainline

[f2fs-dev] [Bug 210765] F2FS causes access invalid blkaddr

2020-12-17 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210765 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[f2fs-dev] [Bug 210745] kernel crash during umounting a partition with f2fs filesystem

2020-12-18 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210745 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |NEEDINFO CC|

[f2fs-dev] [Bug 210797] resize.f2fs over 2 (LVM) disks corrupts whole filesystem

2020-12-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210797 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[f2fs-dev] [Bug 210795] 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.devices[i].path)

2020-12-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=210795 Chao Yu (c...@kernel.org) changed: What|Removed |Added Status|NEW |ASSIGNED CC|

<    1   2   3   4   5   6   7   >