From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 202989] kernel panic during F2FS GC
Date: Fri, 22 Mar 2019 09:02:01 +0000 [thread overview]
Message-ID: <bug-202989-202145-PxiH2o3HQV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202989-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202989
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #3 from Chao Yu (chao@kernel.org) ---
(In reply to Lianjun Huang from comment #2)
> (In reply to Chao Yu from comment #1)
> > Could you list related kernel source code link address? and please use last
> > fsck.f2fs to check whether image was corrupted.
>
> I am sorry but there is no public URL for the source code. The kernel
Oops, at least please pasting related source code at below places:
- f2fs_submit_page_bio()
- /ap/kernel/msm-4.14/fs/f2fs/segment.h:654
BTW, it will be hard for me to figure out the root cause if there is any other
private modification in your 4.14.81 kernel, such as Qualcomm's inline
encryption...
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-03-22 9:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 14:39 [Bug 202989] New: kernel panic during F2FS GC bugzilla-daemon
2019-03-22 2:07 ` [Bug 202989] " bugzilla-daemon
2019-03-22 4:08 ` bugzilla-daemon
2019-03-22 9:02 ` bugzilla-daemon [this message]
2019-03-22 9:24 ` bugzilla-daemon
2019-03-22 9:26 ` bugzilla-daemon
2019-03-22 9:27 ` bugzilla-daemon
2019-03-23 2:51 ` bugzilla-daemon
2019-03-23 7:38 ` [Bug 202989] [MSM-4.14] " bugzilla-daemon
2019-03-25 3:38 ` bugzilla-daemon
2019-03-25 3:46 ` Chao Yu
2019-03-25 12:56 ` Sahitya Tummala
2019-03-25 4:02 ` 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-202989-202145-PxiH2o3HQV@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 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).