From: Chao Yu <chao2.yu@samsung.com>
To: "'Huang, Ying'" <ying.huang@intel.com>
Cc: "'Jaegeuk Kim'" <jaegeuk@kernel.org>,
lkp@01.org, "'LKML'" <linux-kernel@vger.kernel.org>
Subject: RE: [LKP] [lkp] [f2fs] 75cd4e098d: xfstests.generic.042.fail
Date: Mon, 04 Jan 2016 09:12:09 +0800 [thread overview]
Message-ID: <000401d1468d$05bbecb0$1133c610$@samsung.com> (raw)
In-Reply-To: <87egdyqjty.fsf@yhuang-dev.intel.com>
Hi Ying,
> -----Original Message-----
> From: Huang, Ying [mailto:ying.huang@intel.com]
> Sent: Monday, January 04, 2016 8:17 AM
> To: Chao Yu
> Cc: 'Jaegeuk Kim'; lkp@01.org; 'LKML'
> Subject: Re: [LKP] [lkp] [f2fs] 75cd4e098d: xfstests.generic.042.fail
>
> Hi, Yu,
>
> Chao Yu <chao2.yu@samsung.com> writes:
>
> > Hi Ying,
> >
> >> -----Original Message-----
> >> From: kernel test robot [mailto:ying.huang@linux.intel.com]
> >> Sent: Monday, December 28, 2015 9:40 AM
> >> To: Chao Yu
> >> Cc: lkp@01.org; LKML; Jaegeuk Kim
> >> Subject: [lkp] [f2fs] 75cd4e098d: xfstests.generic.042.fail
> >>
> >> FYI, we noticed the below changes on
> >>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> >> commit 75cd4e098d178433436abce08146a21647bb4585 ("f2fs: support FALLOC_FL_ZERO_RANGE")
> >>
> >> We found after your commit, the xfstests test case 009/042 failed.
> >
> > Thank you for the report, 042 is a known issue, IIRC, the reason is f2fs
> > will flush inode page with last i_size in ioctl(F2FS_IOC_SHUTDOWN, 0x01),
> > but 042 expects an zero-sized inode. So I supposed it happened due to the
> > different semantics of metadata flushing between f2fs and xfs.
> >
> > For 009, I haven't saw it failed for long time, did you test with last f2fs?
>
> We tested the specified commit,
Alright, I will have a look at 009 testcase to make sure whether it is
an unfixed issue?
so you mean the latest f2fs-tools?
I mean last f2fs kernel code.
Thanks,
>
> Best Regards,
> Huang, Ying
>
> > Thanks,
> >
> >>
> >>
> =========================================================================================
> >> compiler/disk/fs/kconfig/rootfs/tbox_group/test/testcase:
> >>
> >>
> gcc-4.9/4HDD/f2fs/x86_64-rhel/debian-x86_64-2015-02-07.cgz/vm-kbuild-4G/generic-quick/xfst
> >> ests
> >>
> >> commit:
> >> b4ace33703243fed56f8bfc80a001533acb9decb
> >> 75cd4e098d178433436abce08146a21647bb4585
> >>
> >> b4ace33703243fed 75cd4e098d178433436abce081
> >> ---------------- --------------------------
> >> fail:runs %reproduction fail:runs
> >> | | |
> >> :18 94% 17:18 xfstests.generic.009.fail
> >> :18 94% 17:18 xfstests.generic.042.fail
> >>
> >>
> >> To reproduce:
> >>
> >> git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> >> cd lkp-tests
> >> bin/lkp install job.yaml # job file is attached in this email
> >> bin/lkp run job.yaml
> >>
> >>
> >>
> >> Thanks,
> >> Ying Huang
> >
> > _______________________________________________
> > LKP mailing list
> > LKP@lists.01.org
> > https://lists.01.org/mailman/listinfo/lkp
prev parent reply other threads:[~2016-01-04 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 1:39 kernel test robot
2015-12-31 10:16 ` Chao Yu
2016-01-04 0:17 ` [LKP] " Huang, Ying
2016-01-04 1:12 ` Chao Yu [this message]
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='000401d1468d$05bbecb0$1133c610$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@intel.com \
/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
Powered by JetHome