From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 217266] kernel panic on f2fs filesystem when f2fs_commit_atomic_write
Date: Mon, 03 Apr 2023 17:37:44 +0000 [thread overview]
Message-ID: <bug-217266-202145-4YO1NWk5bg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217266-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217266
--- Comment #7 from michalechner92@googlemail.com ---
Am Mo., 3. Apr. 2023 um 16:08 Uhr schrieb <bugzilla-daemon@kernel.org>:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=217266
>
> Chao Yu (chao@kernel.org) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEW |ASSIGNED
> CC| |chao@kernel.org
>
> --- Comment #5 from Chao Yu (chao@kernel.org) ---
> Hi shilka, Micha L,
>
> Do you have a reproducer?
>
> --
> You may reply to this email to add a comment.
>
> 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
Hey Chao,
I don´t have a reproducer. It just seems to happen randomly while
using the device very rarely.
Am Mo., 3. Apr. 2023 um 19:00 Uhr schrieb <bugzilla-daemon@kernel.org>:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=217266
>
> Jaegeuk Kim (jaegeuk@kernel.org) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |jaegeuk@kernel.org
>
> --- Comment #6 from Jaegeuk Kim (jaegeuk@kernel.org) ---
> I think this fixes the panic.
> https://lore.kernel.org/linux-f2fs-devel/ZCsEytDjqEjQDPiO@google.com/T/#u
>
> --
> You may reply to this email to add a comment.
>
> 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
Hey Jaegeuk,
Thanks for the link and taking a look! I will cherry-pick the fix to
my tree and ship it on the next release on XDA.
I´ll report back in case I get more logs with the panic I shared earlier.
--
You may reply to this email to add a comment.
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
prev parent reply other threads:[~2023-04-03 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 7:01 [f2fs-dev] [Bug 217266] New: kernel panic on f2fs filesystem when f2fs_commit_atomic_write bugzilla-daemon
2023-03-29 17:58 ` [f2fs-dev] [Bug 217266] " bugzilla-daemon
2023-03-30 2:48 ` bugzilla-daemon
2023-03-30 3:31 ` Chao Yu
2023-03-30 7:35 ` Micha L via Linux-f2fs-devel
2023-03-30 3:31 ` bugzilla-daemon
2023-03-30 7:35 ` bugzilla-daemon
2023-04-03 14:07 ` bugzilla-daemon
2023-04-03 16:59 ` bugzilla-daemon
2023-04-03 17:37 ` Micha L via Linux-f2fs-devel
2023-04-03 17:37 ` bugzilla-daemon [this message]
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-217266-202145-4YO1NWk5bg@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 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).