From: Jeff Chua <jeff.chua.linux@gmail.com>
To: Chao Yu <chao@kernel.org>, Yangtao Li <frank.li@vivo.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
Eric Biggers <ebiggers@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
F2FS Development <linux-f2fs-devel@lists.sourceforge.net>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: Fwd: f2fs write error Linux v6.2
Date: Sat, 31 Dec 2022 20:41:34 +0800 [thread overview]
Message-ID: <CAAJw_ZvFvKx+mVd+pWMPVvEnOPkmBBETMqrA_P-3wRGW5HRkDw@mail.gmail.com> (raw)
In-Reply-To: <CAAJw_ZsLjw=+_oju-8Mxy-nEErUYc9ZPfDyX204yiJ7mA8u5gA@mail.gmail.com>
On Sat, Dec 31, 2022 at 7:57 PM Jeff Chua <jeff.chua.linux@gmail.com> wrote:
>
> On Sat, Dec 31, 2022 at 10:51 AM Chao Yu <chao@kernel.org> wrote:
> >
> > Hi Jeff,
> >
> > On 2022/12/30 14:39, Eric Biggers wrote:
> > > 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.
>
> I was just preparing my environment so I could hit the same issue
> before I go for the bisect, so I don't need to reboot every time. Got
> to a point where I could just qemu kvm + initrd ramdisk with / (f2fs)
> and I could hit the problem almost every 8/10 runs just by doing
> "mount -o remount /" and the system would freeze. That's good. I've a
> good test case! ... and then I see Chao Yu's patch ...
>
> > Other than that, I found some cases which can cause similar issue, so I figure
> > out a patch for possible fixing, if you can have a try with it to check whether
> > it can fix your issue, that would be helpful as well.
> >
> > https://lore.kernel.org/linux-f2fs-devel/20221230154332.5082-1-chao@kernel.org/T/#u
>
> Ok, the patch seems to fix the problem. I'll run my qemu kvm
> environment a few more times before I switch the real system. Because
> it's not a that I could cause a real "mount -o remount /" freeze or
> "vi /etc/passwd" fault all the time,
>
> Will feedback soon. This would a very nice year end celebration so I
> could move to 6.2.0-rc1.
Ok, no more freeze, no more errors! All good. I'm finally on the
latest linux-6.2.0-rc1 with the patch.
Happy new year!
My best,
Jeff
next prev parent reply other threads:[~2022-12-31 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAJw_Ztzyh-GNTJYpXbA0CeJv2Rz=fLZKE6_Q=7JMmM+s9yHXQ@mail.gmail.com>
2022-12-24 5:48 ` f2fs write error Linux v6.2 Jeff Chua
2022-12-24 12:43 ` Bagas Sanjaya
2022-12-24 14:00 ` Bagas Sanjaya
2022-12-30 4:04 ` Fwd: " Jeff Chua
2022-12-30 5:56 ` Thorsten Leemhuis
2022-12-30 6:39 ` Eric Biggers
2022-12-30 7:15 ` Yangtao Li
2022-12-31 12:01 ` Jeff Chua
2022-12-31 2:51 ` Chao Yu
2022-12-31 11:57 ` Jeff Chua
2022-12-31 12:41 ` Jeff Chua [this message]
2023-02-17 12:48 ` Linux regression tracking (Thorsten Leemhuis)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAJw_ZvFvKx+mVd+pWMPVvEnOPkmBBETMqrA_P-3wRGW5HRkDw@mail.gmail.com \
--to=jeff.chua.linux@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=frank.li@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).