linux-kernel - Re: Fwd: f2fs write error Linux v6.2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y66Hk6waTeXQDz1/@sol.localdomain>
Date:   Thu, 29 Dec 2022 22:39:15 -0800
From:   Eric Biggers <ebiggers@...nel.org>
To:     Thorsten Leemhuis <regressions@...mhuis.info>
Cc:     Jeff Chua <jeff.chua.linux@...il.com>,
        lkml <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Bagas Sanjaya <bagasdotme@...il.com>,
        Jaegeuk Kim <jaegeuk@...nel.org>, Chao Yu <chao@...nel.org>,
        F2FS Development <linux-f2fs-devel@...ts.sourceforge.net>,
        Linux Regressions <regressions@...ts.linux.dev>
Subject: Re: Fwd: f2fs write error Linux v6.2

On Fri, Dec 30, 2022 at 06:56:36AM +0100, Thorsten Leemhuis wrote:
> On 30.12.22 05:04, Jeff Chua wrote:
> > On 12/24/22 19:43, Bagas Sanjaya wrote:
> >> On Sat, Dec 24, 2022 at 01:48:55PM +0800, Jeff Chua wrote:
> >>> Got the following error in latest linux-6.2-git with just vim (:w
> >>> file1). No problem with linux-6.1.1
> > 
> > What happened to the f2fs developers? No response from anyone yet.
> 
> Well, that indeed is unfortunate and ideally shouldn't happen, but the
> simple reality is: that can happen this time of the year due to this
> thing called "festive season".
> 
> > Am
> > I the only one facing this? Linux-6.2 is unusable until this is fixed.
> > What can I do to help?
> 
> The usual: bisect the issue, as then (a) we know exactly which developer
> caused it, (b) which subsystem/maintainer is responsible (issues in a fs
> might be caused by the VFS, block layer, mm, ...), and (c) might be able
> to quickly revert that culprit, even if the people normally responsible
> are MIA for some reason.
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> 
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.
> 

FWIW, I've tested f2fs on mainline in the last few days, and I haven't seen
this.  The following works fine, for example:

    mkfs.f2fs -f /dev/vdb
    mount /dev/vdb /mnt
    vim
    # write something, then ':w /mnt/file'

If you could provide the mkfs and mount options you are using, and any other
relevant details, that would be helpful.  Bisection would also be very helpful,
as Thorsten mentioned.

- Eric