From: Chao Yu <chao@kernel.org>
To: Jeff Chua <jeff.chua.linux@gmail.com>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Eric Biggers <ebiggers@kernel.org>
Cc: 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 10:51:01 +0800 [thread overview]
Message-ID: <3dd9808e-ffbd-7959-2111-a9f13f2031f1@kernel.org> (raw)
In-Reply-To: <Y66Hk6waTeXQDz1/@sol.localdomain>
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.
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
Thanks,
next prev parent reply other threads:[~2022-12-31 2:51 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 [this message]
2022-12-31 11:57 ` Jeff Chua
2022-12-31 12:41 ` Jeff Chua
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=3dd9808e-ffbd-7959-2111-a9f13f2031f1@kernel.org \
--to=chao@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jeff.chua.linux@gmail.com \
--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).