* [Bug 202989] kernel panic during F2FS GC
2019-03-21 14:39 [Bug 202989] New: kernel panic during F2FS GC bugzilla-daemon
@ 2019-03-22 2:07 ` bugzilla-daemon
2019-03-22 4:08 ` bugzilla-daemon
` (8 subsequent siblings)
9 siblings, 0 replies; 13+ messages in thread
From: bugzilla-daemon @ 2019-03-22 2:07 UTC (permalink / raw)
To: linux-f2fs-devel
https://bugzilla.kernel.org/show_bug.cgi?id=202989
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chao@kernel.org
--- Comment #1 from Chao Yu (chao@kernel.org) ---
Could you list related kernel source code link address? and please use last
fsck.f2fs to check whether image was corrupted.
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug 202989] kernel panic during F2FS GC
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
` (7 subsequent siblings)
9 siblings, 0 replies; 13+ messages in thread
From: bugzilla-daemon @ 2019-03-22 4:08 UTC (permalink / raw)
To: linux-f2fs-devel
https://bugzilla.kernel.org/show_bug.cgi?id=202989
--- Comment #2 from Lianjun Huang (hlianjun@gmail.com) ---
(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 version
is 4.14.81. I will check the image later.
I would like to clarify that kernel panic are from two different machines. And
both new_blkaddr and old_blkaddr of fio are 0xFFFFFFFF.
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug 202989] kernel panic during F2FS GC
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
2019-03-22 9:24 ` bugzilla-daemon
` (6 subsequent siblings)
9 siblings, 0 replies; 13+ messages in thread
From: bugzilla-daemon @ 2019-03-22 9:02 UTC (permalink / raw)
To: linux-f2fs-devel
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.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug 202989] kernel panic during F2FS GC
2019-03-21 14:39 [Bug 202989] New: kernel panic during F2FS GC bugzilla-daemon
` (2 preceding siblings ...)
2019-03-22 9:02 ` bugzilla-daemon
@ 2019-03-22 9:24 ` bugzilla-daemon
2019-03-22 9:26 ` bugzilla-daemon
` (5 subsequent siblings)
9 siblings, 0 replies; 13+ messages in thread
From: bugzilla-daemon @ 2019-03-22 9:24 UTC (permalink / raw)
To: linux-f2fs-devel
https://bugzilla.kernel.org/show_bug.cgi?id=202989
--- Comment #4 from Lianjun Huang (hlianjun@gmail.com) ---
Created attachment 281961
--> https://bugzilla.kernel.org/attachment.cgi?id=281961&action=edit
f2fs_submit_page_bio and the file segment.h
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug 202989] kernel panic during F2FS GC
2019-03-21 14:39 [Bug 202989] New: kernel panic during F2FS GC bugzilla-daemon
` (3 preceding siblings ...)
2019-03-22 9:24 ` bugzilla-daemon
@ 2019-03-22 9:26 ` bugzilla-daemon
2019-03-22 9:27 ` bugzilla-daemon
` (4 subsequent siblings)
9 siblings, 0 replies; 13+ messages in thread
From: bugzilla-daemon @ 2019-03-22 9:26 UTC (permalink / raw)
To: linux-f2fs-devel
https://bugzilla.kernel.org/show_bug.cgi?id=202989
Lianjun Huang (hlianjun@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #281961|f2fs_submit_page_bio and |f2fs_submit_page_bio
description|the file segment.h |
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug 202989] kernel panic during F2FS GC
2019-03-21 14:39 [Bug 202989] New: kernel panic during F2FS GC bugzilla-daemon
` (4 preceding siblings ...)
2019-03-22 9:26 ` bugzilla-daemon
@ 2019-03-22 9:27 ` bugzilla-daemon
2019-03-23 2:51 ` bugzilla-daemon
` (3 subsequent siblings)
9 siblings, 0 replies; 13+ messages in thread
From: bugzilla-daemon @ 2019-03-22 9:27 UTC (permalink / raw)
To: linux-f2fs-devel
https://bugzilla.kernel.org/show_bug.cgi?id=202989
--- Comment #5 from Lianjun Huang (hlianjun@gmail.com) ---
Created attachment 281963
--> https://bugzilla.kernel.org/attachment.cgi?id=281963&action=edit
the file segment.h
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug 202989] kernel panic during F2FS GC
2019-03-21 14:39 [Bug 202989] New: kernel panic during F2FS GC bugzilla-daemon
` (5 preceding siblings ...)
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
` (2 subsequent siblings)
9 siblings, 0 replies; 13+ messages in thread
From: bugzilla-daemon @ 2019-03-23 2:51 UTC (permalink / raw)
To: linux-f2fs-devel
https://bugzilla.kernel.org/show_bug.cgi?id=202989
--- Comment #6 from Chao Yu (chao@kernel.org) ---
> I would like to clarify that kernel panic are from two different machines.
> And both new_blkaddr and old_blkaddr of fio are 0xFFFFFFFF.
Okay, so that we need to add log to track block address return from
f2fs_allocate_data_block(). If it allocates 0xffffffff, should kernel panic in
update_sit_entry() in prior to f2fs_submit_page_bio()?
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug 202989] [MSM-4.14] kernel panic during F2FS GC
2019-03-21 14:39 [Bug 202989] New: kernel panic during F2FS GC bugzilla-daemon
` (6 preceding siblings ...)
2019-03-23 2:51 ` bugzilla-daemon
@ 2019-03-23 7:38 ` bugzilla-daemon
2019-03-25 3:38 ` bugzilla-daemon
2019-03-25 4:02 ` bugzilla-daemon
9 siblings, 0 replies; 13+ messages in thread
From: bugzilla-daemon @ 2019-03-23 7:38 UTC (permalink / raw)
To: linux-f2fs-devel
https://bugzilla.kernel.org/show_bug.cgi?id=202989
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|kernel panic during F2FS GC |[MSM-4.14] kernel panic
| |during F2FS GC
--- Comment #7 from Chao Yu (chao@kernel.org) ---
I've changed this issue's title to indicate it is from private code repo.
Could you add to Cc below email address of qualcomm's guys, since maybe they
can provide some help.
stummala@codeaurora.org
riteshh@codeaurora.org
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug 202989] [MSM-4.14] kernel panic during F2FS GC
2019-03-21 14:39 [Bug 202989] New: kernel panic during F2FS GC bugzilla-daemon
` (7 preceding siblings ...)
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 4:02 ` bugzilla-daemon
9 siblings, 1 reply; 13+ messages in thread
From: bugzilla-daemon @ 2019-03-25 3:38 UTC (permalink / raw)
To: linux-f2fs-devel
https://bugzilla.kernel.org/show_bug.cgi?id=202989
--- Comment #8 from Lianjun Huang (hlianjun@gmail.com) ---
(In reply to Chao Yu from comment #7)
> I've changed this issue's title to indicate it is from private code repo.
It is OK.
>
> Could you add to Cc below email address of qualcomm's guys, since maybe they
> can provide some help.
>
> stummala@codeaurora.org
> riteshh@codeaurora.org
I failed to CC the email addresses above, they seem not to register kernel
Bugzilla.
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bug 202989] [MSM-4.14] kernel panic during F2FS GC
2019-03-25 3:38 ` bugzilla-daemon
@ 2019-03-25 3:46 ` Chao Yu
2019-03-25 12:56 ` Sahitya Tummala
0 siblings, 1 reply; 13+ messages in thread
From: Chao Yu @ 2019-03-25 3:46 UTC (permalink / raw)
To: Sahitya Tummala, Ritesh Harjani; +Cc: bugzilla-daemon, linux-f2fs-devel
On 2019/3/25 11:38, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=202989
>
> --- Comment #8 from Lianjun Huang (hlianjun@gmail.com) ---
> (In reply to Chao Yu from comment #7)
>> I've changed this issue's title to indicate it is from private code repo.
> It is OK.
>
>>
>> Could you add to Cc below email address of qualcomm's guys, since maybe they
>> can provide some help.
>>
>> stummala@codeaurora.org
>> riteshh@codeaurora.org
>
> I failed to CC the email addresses above, they seem not to register kernel
> Bugzilla.
Let me Cc them directly. :)
To Sahitya, Ritesh
Do you have time to take a look at this issue?
Thanks,
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bug 202989] [MSM-4.14] kernel panic during F2FS GC
2019-03-25 3:46 ` Chao Yu
@ 2019-03-25 12:56 ` Sahitya Tummala
0 siblings, 0 replies; 13+ messages in thread
From: Sahitya Tummala @ 2019-03-25 12:56 UTC (permalink / raw)
To: Chao Yu; +Cc: bugzilla-daemon, linux-f2fs-devel
On Mon, Mar 25, 2019 at 11:46:59AM +0800, Chao Yu wrote:
> On 2019/3/25 11:38, bugzilla-daemon@bugzilla.kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=202989
> >
> > --- Comment #8 from Lianjun Huang (hlianjun@gmail.com) ---
> > (In reply to Chao Yu from comment #7)
> >> I've changed this issue's title to indicate it is from private code repo.
> > It is OK.
> >
> >>
> >> Could you add to Cc below email address of qualcomm's guys, since maybe they
> >> can provide some help.
> >>
> >> stummala@codeaurora.org
> >> riteshh@codeaurora.org
> >
> > I failed to CC the email addresses above, they seem not to register kernel
> > Bugzilla.
>
> Let me Cc them directly. :)
>
> To Sahitya, Ritesh
>
> Do you have time to take a look at this issue?
Sure, Chao.
Lianjun,
Can you report this issue through Qualcomm customer support portal and share the
ramdumps for the same?
Also, share the test scenario where this issue was observed.
Thanks,
Sahitya.
>
> Thanks,
>
> >
--
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug 202989] [MSM-4.14] kernel panic during F2FS GC
2019-03-21 14:39 [Bug 202989] New: kernel panic during F2FS GC bugzilla-daemon
` (8 preceding siblings ...)
2019-03-25 3:38 ` bugzilla-daemon
@ 2019-03-25 4:02 ` bugzilla-daemon
9 siblings, 0 replies; 13+ messages in thread
From: bugzilla-daemon @ 2019-03-25 4:02 UTC (permalink / raw)
To: linux-f2fs-devel
https://bugzilla.kernel.org/show_bug.cgi?id=202989
--- Comment #9 from yuchao0@huawei.com ---
On 2019/3/25 11:38, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=202989
>
> --- Comment #8 from Lianjun Huang (hlianjun@gmail.com) ---
> (In reply to Chao Yu from comment #7)
>> I've changed this issue's title to indicate it is from private code repo.
> It is OK.
>
>>
>> Could you add to Cc below email address of qualcomm's guys, since maybe they
>> can provide some help.
>>
>> stummala@codeaurora.org
>> riteshh@codeaurora.org
>
> I failed to CC the email addresses above, they seem not to register kernel
> Bugzilla.
Let me Cc them directly. :)
To Sahitya, Ritesh
Do you have time to take a look at this issue?
Thanks,
>
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 13+ messages in thread