public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: vasily isaenko <vasily.isaenko@oracle.com>,
	ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v2] fallocate04: another check if SEEK_HOLE is not supported
Date: Thu, 21 May 2015 09:26:37 +0800	[thread overview]
Message-ID: <1432171597.16347.53.camel@G08FNSTD140232> (raw)
In-Reply-To: <1089771258.2559286.1432121544985.JavaMail.zimbra@redhat.com>

On Wed, 2015-05-20 at 07:32 -0400, Jan Stancek wrote:

[...]
> > > > How about put them before lseek(SEEK_HOLE) ?
> > > 
> > > I think we should do the check on all kernels. lseek() can only check that
> > > the
> > > hole exists, but current check also verifies that hole has correct size and
> > > content.
> > > 
> > 
> > Right. It is the strict way we need to do. But it would make the test
> > complex.
> 
> I think we already check it strictly, see line 172-177. This covers blocks 1,2,3.
> The patch you proposed _adds_ one more check only for zero-ed block 2.
> My objection was that this seems redundant, because we already have
> a check (line 172-177), which covers all 3 blocks. Am I missing something?
> 

Oh, I see. I misunderstand your reply previous. Right, the patch is
redundant.
Thank you.

> > Now, "turn that warning into TINFO" looks simple but effective.
> > If nobody reject, I will send new patch like:
> 
> Looks OK to me, though maybe it should TBROK on kernels > 3.1 even when
> errno is EINVAL.

OK. I will fix it at the same time.

Thanks.

Best regards,
Zeng

> 
> Regards,
> Jan
> 
> > 
> > -               tst_resm(TWARN | TERRNO, "lseek() doesn't support
> > SEEK_HOLE");
> > +               if (tst_kvercmp(3, 1, 0) < 0)
> > +                       tst_resm(TINFO, "lseek() doesn't support SEEK_HOLE, "
> > +                               "this is expected for < 3.1 kernels");
> > +       } else {
> > +               tst_resm(TINFO, "found a hole at '%ld' offset", ret);
> >         }
> > -       tst_resm(TINFO, "found a hole at '%ld' offset", ret);
> > 
> > Thank you.
> > 
> > Best regards,
> > Zeng
> > 
> > 
> > > Regards,
> > > Jan
> > [...]
> > 
> > 



------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2015-05-21  1:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 13:05 [LTP] [PATCH v4] syscalls/fallocate04: add new fallocate() test Alexey Kodanev
2015-04-23  7:44 ` Jan Stancek
2015-04-27 14:07 ` Cyril Hrubis
     [not found]   ` <553E55D3.7070001@oracle.com>
2015-04-27 15:27     ` Cyril Hrubis
2015-05-18 10:14 ` [LTP] [PATCH] fallocate04: another check if SEEK_HOLE is not supported Zeng Linggang
2015-05-18 14:03   ` Alexey Kodanev
2015-05-19  8:50     ` [LTP] [PATCH v2] " Zeng Linggang
2015-05-19 11:18       ` Jan Stancek
2015-05-20  1:47         ` Zeng Linggang
2015-05-20  6:52           ` Jan Stancek
2015-05-20  9:58             ` Zeng Linggang
2015-05-20 11:32               ` Jan Stancek
2015-05-21  1:26                 ` Zeng Linggang [this message]
2015-05-20  8:13           ` Alexey Kodanev
2015-05-20  9:35             ` Zeng Linggang
2015-05-21  5:39 ` [LTP] [PATCH] fallocate04: Use tst_kvercmp after lseek(SEEK_HOLE) return EINVAL Zeng Linggang
2015-05-22 14:21   ` Jan Stancek
2015-06-04 11:35     ` Alexey Kodanev
2015-06-04 11:52       ` Jan Stancek

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=1432171597.16347.53.camel@G08FNSTD140232 \
    --to=zenglg.jy@cn.fujitsu.com \
    --cc=jstancek@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vasily.isaenko@oracle.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