From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: [f2fs-dev] [GIT PULL] f2fs fix for 5.19-rc4
Date: Fri, 24 Jun 2022 17:40:58 -0700 [thread overview]
Message-ID: <YrZZmp8qBSDM28iy@google.com> (raw)
Hi Linus,
Could you please consider this pull request?
Thanks,
The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-5.19-rc4
for you to fetch changes up to 82c7863ed95d0914f02c7c8c011200a763bc6725:
f2fs: do not count ENOENT for error case (2022-06-21 08:29:56 -0700)
----------------------------------------------------------------
f2fs-fix-5.19
This includes some urgent fixes to avoid generating corrupted inodes
caused by compressed and inline_data files. In addition, another patch
tries to avoid wrong error report which prevents a roll-forward
recovery.
----------------------------------------------------------------
Daeho Jeong (1):
f2fs: fix iostat related lock protection
Jaegeuk Kim (2):
f2fs: attach inline_data after setting compression
f2fs: do not count ENOENT for error case
fs/f2fs/iostat.c | 31 ++++++++++++++++++-------------
fs/f2fs/namei.c | 17 +++++++++++------
fs/f2fs/node.c | 4 +++-
3 files changed, 32 insertions(+), 20 deletions(-)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: [GIT PULL] f2fs fix for 5.19-rc4
Date: Fri, 24 Jun 2022 17:40:58 -0700 [thread overview]
Message-ID: <YrZZmp8qBSDM28iy@google.com> (raw)
Hi Linus,
Could you please consider this pull request?
Thanks,
The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-5.19-rc4
for you to fetch changes up to 82c7863ed95d0914f02c7c8c011200a763bc6725:
f2fs: do not count ENOENT for error case (2022-06-21 08:29:56 -0700)
----------------------------------------------------------------
f2fs-fix-5.19
This includes some urgent fixes to avoid generating corrupted inodes
caused by compressed and inline_data files. In addition, another patch
tries to avoid wrong error report which prevents a roll-forward
recovery.
----------------------------------------------------------------
Daeho Jeong (1):
f2fs: fix iostat related lock protection
Jaegeuk Kim (2):
f2fs: attach inline_data after setting compression
f2fs: do not count ENOENT for error case
fs/f2fs/iostat.c | 31 ++++++++++++++++++-------------
fs/f2fs/namei.c | 17 +++++++++++------
fs/f2fs/node.c | 4 +++-
3 files changed, 32 insertions(+), 20 deletions(-)
next reply other threads:[~2022-06-25 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 0:40 Jaegeuk Kim [this message]
2022-06-25 0:40 ` [GIT PULL] f2fs fix for 5.19-rc4 Jaegeuk Kim
2022-06-25 18:30 ` [f2fs-dev] " pr-tracker-bot
2022-06-25 18:30 ` pr-tracker-bot
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=YrZZmp8qBSDM28iy@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.