From: ARAI Shun-ichi <hermes@ceres.dti.ne.jp>
To: linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8 in nilfs_segctor_do_construct
Date: Sun, 16 Feb 2020 11:10:29 +0900 (JST) [thread overview]
Message-ID: <20200216.111029.687350152614907818.hermes@ceres.dti.ne.jp> (raw)
In-Reply-To: <20200210.224609.499887311281343618.hermes@ceres.dti.ne.jp>
And,
In <20200210.224609.499887311281343618.hermes@ceres.dti.ne.jp>;
ARAI Shun-ichi <hermes@ceres.dti.ne.jp> wrote
as Subject "Re: BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8 in nilfs_segctor_do_construct":
> Hi,
>
> FYI, reporting additional test results.
>
> I reproduced this problem with clean NILFS2 fs in previous mail.
> "clean" means that "make filesystem before every tests."
> In this mail, I tried to reproduct with/without VG/LV, LUKS, loopback.
>
> * Not reproduced
> USB stick - primary partition - NILFS2
> USB stick - primary partition - VG/LV - NILFS2
> USB stick - primary partition - VG/LV - LUKS - NILFS2
> USB stick - primary partition - LUKS - VG/LV - NILFS2
> USB stick - primary partition - LUKS - VG/LV - LUKS - NILFS2
> /tmp (tmpfs) - regular file - NILFS2 (loopback mount, kernel 4.19.82)
> USB stick - primary partition(512MiB) - NILFS2
>
> * Reproduced (always, immediately)
> /tmp (tmpfs) - regular file - NILFS2 (loopback mount)
> USB stick - primary partition - ext4 - regular file - NILFS2 (loopback mount)
this loopback problem is seen in Kernel 5.5.4.
> Test conditions:
> kernel 4.19.86 (same as previous test)
> NILFS2/ext4 filesystem, VG/LV, LUKS were made with default parameters
> size of "primary partition" in USB stick is approx. 14GiB
> size of "regular file" is approx. 512MiB
> "reproduce": mount NILFS2, touch file, sync
next prev parent reply other threads:[~2020-02-16 2:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 17:34 BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8 in nilfs_segctor_do_construct Tomas Hlavaty
2019-11-18 16:51 ` Ryusuke Konishi
2019-11-19 6:04 ` Viacheslav Dubeyko
2020-01-23 13:00 ` Tomas Hlavaty
2019-12-19 21:02 ` Tomas Hlavaty
2020-01-23 12:31 ` Tomas Hlavaty
2020-03-27 6:26 ` Tomas Hlavaty
[not found] ` <CAKFNMomjWkNvHvHkEp=Jv_BiGPNj=oLEChyoXX1yCj5xctAkMA@mail.gmail.com>
2020-03-28 9:26 ` ARAI Shun-ichi
2020-04-30 12:38 ` BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8 in nilfs_segctor_do_co Hideki EIRAKU
2020-04-30 15:27 ` Tom
2020-05-31 17:49 ` Ryusuke Konishi
[not found] ` <20200601024013.1296-1-hdanton@sina.com>
2020-06-01 11:46 ` Ryusuke Konishi
2020-01-23 13:58 ` BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8 in nilfs_segctor_do_construct ARAI Shun-ichi
2020-01-23 14:30 ` ARAI Shun-ichi
2020-02-10 13:46 ` ARAI Shun-ichi
2020-02-16 2:10 ` ARAI Shun-ichi [this message]
2020-02-16 2:24 ` Brian G.
2020-02-16 3:59 ` Ryusuke Konishi
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=20200216.111029.687350152614907818.hermes@ceres.dti.ne.jp \
--to=hermes@ceres.dti.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
/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).