From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 205181] kernel panic when accessing btrfs root device with f2fs in kernel
Date: Sun, 13 Oct 2019 15:49:32 +0000 [thread overview]
Message-ID: <bug-205181-202145-6EjFsxbCvJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205181-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205181
Andrew Macks (andypoo@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andypoo@gmail.com
--- Comment #2 from Andrew Macks (andypoo@gmail.com) ---
The issue is present in 4.14 longterm, 4.19 longterm and 5.2 stable EOL.
The cause is the following patch:
July 2: Original commit
10f966bbf521bb9b2e497bbca496a5141f4071d0
f2fs: use generic EFSBADCRC/EFSCORRUPTED
July 12: Merged into mainline with f2fs-for-5.3
July 28: Fix from Icenowy Zheng (read this for some background)
38fb6d0ea34299d97b031ed64fe994158b6f8eb3
f2fs: use EINVAL for superblock with invalid magic
July 30: Fix merged into mainline with f2fs-for-5.4-rc3 (note the typo in
branch name, this was actually for 5.3-rc3)
September 15: Kernel 5.3 was born so already contained the fix.
It was backported into the relevant branches below:
October 1: Original commit merged into 5.2.18
5.2.18 (5.2.19, 5.2.20, 5.2.21 EOL still affected)
c704eb3aaffae0d6463b1773b37e69695b112ca4
f2fs: use generic EFSBADCRC/EFSCORRUPTED
October 1: Original commit merged into 4.19.76
4.19.76 (4.19.77, 4.19.78, 4.19.79 still affected)
59a5cea41dd0ae706ab83f8ecd64199aadefb493
f2fs: use generic EFSBADCRC/EFSCORRUPTED
October 5: Original commit merged into 4.14.147
4.14.147 (4.14.148 and 4.14.149 still affected)
e991f02f6f9117514ed1374b39ce195013ab9cd0
f2fs: use generic EFSBADCRC/EFSCORRUPTED
...
Further notes:
* To date, 4.14, 4.19 and 5.2 all contain the issue.
* The f2fs development/stable kernel branches contain a fix (including their
4.14 and 4.19 branches), so the issue is not present there.
* Not quite sure why this commit was backported at all to longterm, but maybe I
am missing some behavioural change which warranted it. (To me, it seems like
this was long-standing functionality already).
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-10-13 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 13:13 [f2fs-dev] [Bug 205181] New: kernel panic when accessing btrfs root device with f2fs in kernel bugzilla-daemon
2019-10-13 14:08 ` [f2fs-dev] [Bug 205181] " bugzilla-daemon
2019-10-13 15:49 ` bugzilla-daemon [this message]
2019-10-13 16:19 ` bugzilla-daemon
2019-10-19 17:29 ` bugzilla-daemon
2019-10-31 18:14 ` bugzilla-daemon
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=bug-205181-202145-6EjFsxbCvJ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.