Bug#1021927: >= Kernel 5.19 reports corrupted f2fs without apparent actual corruption

2025-02-25 Thread Chao Yu
On 2/26/25 01:57, Salvatore Bonaccorso wrote: > Hi > > I do realize the subject was badly choosed so replying again with a > better subject. The downstream Debian report can be found at > https://bugs.debian.org/1021927 Hi Salvatore, Please don't worry, fsck has checked your device and reported

Bug#1063422: [regression 6.1.y] f2fs: invalid zstd compress level: 6

2024-02-19 Thread Chao Yu
On 2024/2/20 3:54, Salvatore Bonaccorso wrote: Hi, On Mon, Feb 19, 2024 at 10:35:13AM +0800, Chao Yu wrote: On 2024/2/9 4:19, Salvatore Bonaccorso wrote: Hi Jaegeuk Kim, Chao Yu, In Debian the following regression was reported after a Dhya updated to 6.1.76: On Wed, Feb 07, 2024 at 10:43

Bug#1063422: [regression 6.1.y] f2fs: invalid zstd compress level: 6

2024-02-18 Thread Chao Yu
On 2024/2/9 4:19, Salvatore Bonaccorso wrote: Hi Jaegeuk Kim, Chao Yu, In Debian the following regression was reported after a Dhya updated to 6.1.76: On Wed, Feb 07, 2024 at 10:43:47PM -0500, Dhya wrote: Package: src:linux Version: 6.1.76-1 Severity: critical Justification: breaks the whole

Bug#955549: [f2fs-dev] Bug#955549: f2fs-tools: fsck.f2fs segfaults

2020-04-14 Thread Chao Yu
On 2020/4/10 7:32, Adam Borowski wrote: > On Tue, Apr 07, 2020 at 06:22:19PM +0800, Chao Yu wrote: >> I figured out two patches to fix segfault issues, could you please have >> a try: >> >> fsck.f2fs: fix to check validation of i_xattr_nid >> fsck.f2fs:

Bug#955549: [f2fs-dev] Bug#955549: f2fs-tools: fsck.f2fs segfaults

2020-04-07 Thread Chao Yu
14:37, Chao Yu wrote: > Thanks for forwarding, Ted. > > On 2020/4/3 10:45, Adam Borowski wrote: >> On Thu, Apr 02, 2020 at 03:16:58PM -0400, Theodore Y. Ts'o wrote: >>> On Thu, Apr 02, 2020 at 02:01:26PM +0200, Adam Borowski wrote: >>>> >>>> After

Bug#955549: [f2fs-dev] Bug#955549: f2fs-tools: fsck.f2fs segfaults

2020-04-02 Thread Chao Yu
Thanks for forwarding, Ted. On 2020/4/3 10:45, Adam Borowski wrote: > On Thu, Apr 02, 2020 at 03:16:58PM -0400, Theodore Y. Ts'o wrote: >> On Thu, Apr 02, 2020 at 02:01:26PM +0200, Adam Borowski wrote: >>> >>> After a lot of output on a damaged filesystem (SD card copied to an image) >>> fsck.f2fs