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 6.2-rc3
Date: Wed, 4 Jan 2023 10:39:41 -0800 [thread overview]
Message-ID: <Y7XH7fSoURcqoUQW@google.com> (raw)
Hi Linus,
Could you please consider this pull request?
Thanks,
The following changes since commit 69b41ac87e4a664de78a395ff97166f0b2943210:
Merge tag 'for-6.2-rc2-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux (2023-01-02 11:06:18 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-fix-6.2-rc3
for you to fetch changes up to df9d44b645b83fffccfb4e28c1f93376585fdec8:
f2fs: let's avoid panic if extent_tree is not created (2023-01-03 08:59:06 -0800)
----------------------------------------------------------------
f2fs-fix-6.2-rc3
This series fixes the below three bugs introduced in 6.2-rc1.
- fix a null pointer dereference in f2fs_issue_flush, which occurs by the
combination of mount/remount options.
- fix a bug in per-block age-based extent_cache newly introduced in 6.2-rc1,
which reported a wrong age information in extent_cache.
- fix a kernel panic if extent_tree was not created, which was caught by a
wrong BUG_ON.
----------------------------------------------------------------
Chao Yu (1):
f2fs: fix to avoid NULL pointer dereference in f2fs_issue_flush()
Jaegeuk Kim (4):
f2fs: initialize extent_cache parameter
f2fs: don't mix to use union values in extent_info
f2fs: should use a temp extent_info for lookup
f2fs: let's avoid panic if extent_tree is not created
fs/f2fs/data.c | 2 +-
fs/f2fs/extent_cache.c | 34 ++++++++++++++++++----------------
fs/f2fs/file.c | 2 +-
fs/f2fs/segment.c | 13 +++++--------
4 files changed, 25 insertions(+), 26 deletions(-)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2023-01-04 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 18:39 Jaegeuk Kim [this message]
2023-01-04 20:17 ` [f2fs-dev] [GIT PULL] f2fs fix for 6.2-rc3 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=Y7XH7fSoURcqoUQW@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 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).