From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 202989] kernel panic during F2FS GC
Date: Sat, 23 Mar 2019 02:51:21 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from [172.30.20.202] (helo=mx.sourceforge.net)
by sfs-ml-4.v29.lw.sourceforge.com with esmtps
(TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1)
(envelope-from )
id 1h7Wkt-0008Ae-Sy
for linux-f2fs-devel@lists.sourceforge.net; Sat, 23 Mar 2019 02:51:31 +0000
Received: from mail.wl.linuxfoundation.org ([198.145.29.98])
by sfi-mx-3.v28.lw.sourceforge.com with esmtps
(TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1)
id 1h7Wkq-004ymv-6y
for linux-f2fs-devel@lists.sourceforge.net; Sat, 23 Mar 2019 02:51:29 +0000
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 8F4952A1AD
for ;
Sat, 23 Mar 2019 02:51:21 +0000 (UTC)
In-Reply-To:
List-Id:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net
To: linux-f2fs-devel@lists.sourceforge.net
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.