linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Chua <jeff.chua.linux@gmail.com>
To: Yangtao Li <frank.li@vivo.com>
Cc: ebiggers@kernel.org, bagasdotme@gmail.com, chao@kernel.org,
	jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, regressions@leemhuis.info,
	regressions@lists.linux.dev, torvalds@linux-foundation.org
Subject: Re: Fwd: f2fs write error Linux v6.2
Date: Sat, 31 Dec 2022 20:01:27 +0800	[thread overview]
Message-ID: <CAAJw_Zs7W5yToJ0L0eB55Ch30k-E1+L_B9YHHv9LTCVhHM7LCQ@mail.gmail.com> (raw)
In-Reply-To: <20221230071551.61833-1-frank.li@vivo.com>

On Fri, Dec 30, 2022 at 3:16 PM Yangtao Li <frank.li@vivo.com> wrote:
>
> > What happened to the f2fs developers? No response from anyone yet. Am
> > I the only one facing this? Linux-6.2 is unusable until this is fixed.
> > What can I do to help?
>
> It's been a long time since I saw Kim and Chao respond to messages. I think
> it may be because of the holiday in the US，and China loosened restrictions
> on COVID-19 (lots of people got sick, I just recovered today).
>
> BTW, the log you uploaded corresponds to which kernel git is, and which
> commit it corresponds to.

Using the latest git pull ...

commit c8451c141e07a8d05693f6c8d0e418fbb4b68bb7 (HEAD -> master,
origin/master, origin/HEAD)
Merge: 262eef26e350 0948a9ef1d59
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Dec 30 10:47:25 2022 -0800


I just applied Chao Yu's patch and it seems to hold ..

Thank you! Happy New Year!

Jeff

  reply	other threads:[~2022-12-31 12:01 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 [this message]
2022-12-31  2:51             ` Chao Yu
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=CAAJw_Zs7W5yToJ0L0eB55Ch30k-E1+L_B9YHHv9LTCVhHM7LCQ@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).