Re: [ext4] 079f9927c7: ltp.mmap16.fail

Re: [ext4] 079f9927c7: ltp.mmap16.fail

[Theodore Ts'o]

On Wed, May 29, 2019 at 10:52:56AM +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
> 
> commit: 079f9927c7bfa026d963db1455197159ebe5b534 ("ext4: gracefully handle ext4_break_layouts() failure during truncate")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

Jan --- this is the old version of your patch, which I had dropped
before sending a push request to Linus.  However, I forgot to reset
the dev branch so it still had the old patch on it, and so it got
picked up in linux-next.  Apologies for the confusion.

I've reset the dev branch on ext4.git, and the new version of your
patch will show up there shortly, as I start reviewing patches for the
next merge window.

Cheers,

					- Ted

> <<<test_start>>>
> tag=mmap16 stime=1559078706
> cmdline="mmap16"
> contacts=""
> analysis=exit
> <<<test_output>>>
> mke2fs 1.43.4 (31-Jan-2017)
> mmap16      0  TINFO  :  Using test device LTP_DEV='/dev/loop0'
> mmap16      0  TINFO  :  Formatting /dev/loop0 with ext4 opts='-b 1024' extra opts='10240'
> mmap16      1  TFAIL  :  mmap16.c:85: Bug is reproduced!
> <<<execution_status>>>
> initiation_status="ok"
> duration=8 termination_type=exited termination_id=1 corefile=no
> cutime=11 cstime=345
> <<<test_end>>>

Re: [LKP] [ext4] 079f9927c7: ltp.mmap16.fail

[Naresh Kamboju]

Hi Ted,

On Wed, 29 May 2019 at 09:26, Theodore Ts'o <tytso@mit.edu> wrote:
>
> On Wed, May 29, 2019 at 10:52:56AM +0800, kernel test robot wrote:
> > FYI, we noticed the following commit (built with gcc-7):
> >
> > commit: 079f9927c7bfa026d963db1455197159ebe5b534 ("ext4: gracefully handle ext4_break_layouts() failure during truncate")
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

I do have found this problem on linux next 20190528 on x86_64, i386,
arm64 and arm architectures.
But, this failure is not easy to reproduce.
so thought of sharing report with steps to reproduce and got delayed.

>
> Jan --- this is the old version of your patch, which I had dropped
> before sending a push request to Linus.  However, I forgot to reset
> the dev branch so it still had the old patch on it, and so it got
> picked up in linux-next.  Apologies for the confusion.
>
> I've reset the dev branch on ext4.git, and the new version of your
> patch will show up there shortly, as I start reviewing patches for the
> next merge window.

However, Thanks for looking into this problem.
I will keep monitoring this mmap16 failure and let you know when it
will get fixed.

- Naresh