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: Thu, 30 Mar 2023 07:35:59 +0000 [thread overview]
Message-ID: <bug-217266-202145-7MFpPGDJIf@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 #4 from michalechner92@googlemail.com ---
Am Do., 30. März 2023 um 05:31 Uhr schrieb Chao Yu <chao@kernel.org>:
>
> On 2023/3/30 10:48, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=217266
> >
> > --- Comment #2 from shilka (shilkazx@gmail.com) ---
> > (In reply to michalechner92 from comment #1)
> >> That looks identical to what I reported last week here:
> >>
> >> https://sourceforge.net/p/linux-f2fs/mailman/message/37794257/
>
> Could you please have a try w/ below patch?
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a46bebd502fe1a3bd1d22f64cedd93e7e7702693
>
Hello Chao,
Thanks for the answer.
The crashes were reported to me after I merged the latest f2fs-stable
patches for 5.10 from
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-stable.git/log/?h=linux-5.10.y
Which includes the commit you just mentioned
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-stable.git/commit/?h=linux-5.10.y&id=720709c3276220fdb70e9385d87c6169476f04e7
My source is here:
https://github.com/freak07/Kirisakura_Pantah/commits/pantah-tq2a.230305/fs/f2fs
The crashes were reported to me after I merged the latest tag of
f2fs-stable, if you look back through my history on March 4th and
March 11th.
I reverted the latest f2fs-stable patches on march 23rd and didn´t
receive a further report of the crash so far.
> >>
> >>
> >
> > Yep, it seems very similar, but I do not encounter this problem until
> update to
> > kernel 6.2.8.
> > Before I saw your reply, I guess there might exist some subtle conflicts
> > between new feature in 6.2.8 kernel and the f2fs module. With your info, it
> is
> > highly possible that the implementation of f2fs exists some bug, and new
> kernel
> > feature might frequently trigger it.
> >
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
--
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
next prev parent reply other threads:[~2023-03-30 7:36 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 [this message]
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
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-7MFpPGDJIf@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 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.