From: Theodore Ts'o <tytso@mit.edu>
To: ltp@lists.linux.it
Subject: [LTP] [ext4] 079f9927c7: ltp.mmap16.fail
Date: Tue, 28 May 2019 23:56:13 -0400 [thread overview]
Message-ID: <20190529035613.GA6210@mit.edu> (raw)
In-Reply-To: <20190529025256.GB22325@shao2-debian>
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>>>
next prev parent reply other threads:[~2019-05-29 3:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 2:52 [LTP] [ext4] 079f9927c7: ltp.mmap16.fail kernel test robot
2019-05-29 3:56 ` Theodore Ts'o [this message]
2019-05-29 8:04 ` [LTP] [LKP] " Naresh Kamboju
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=20190529035613.GA6210@mit.edu \
--to=tytso@mit.edu \
--cc=ltp@lists.linux.it \
/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