public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 2/2] Replace struct event_t with struct inotify_event
Date: Thu, 05 Apr 2012 09:39:39 +0800	[thread overview]
Message-ID: <4F7CF7DB.2080802@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.BSF.2.00.1204041738350.25027@toaster.local>

On 04/05/2012 08:42 AM, Garrett Cooper wrote:

> Replace struct event_t with struct inotify_event
> 
> Also do some minor whitespace cleanup while I'm
> in the neighborhood.


Cooper,

there's something wrong with this patch, please take a look at the ".name".

inotify02    1  TPASS  :  get event: wd=1 mask=40000004 cookie=0 len=0 name="\x01"
inotify02    2  TFAIL  :  get event: wd=1 mask=100 (expected 100) cookie=0 len=16 name="test_file1" (expected "test ") -63
inotify02    3  TFAIL  :  get event: wd=1 mask=20 (expected 20) cookie=0 len=16 name="test_file1" (expected "tes") -87
inotify02    4  TFAIL  :  get event: wd=1 mask=8 (expected 8) cookie=0 len=16 name="test_file1" (expected "test@") -31
inotify02    5  TFAIL  :  get event: wd=1 mask=40 (expected 40) cookie=1950 len=16 name="test_file1" (expected "test�") 33
inotify02    6  TFAIL  :  get event: wd=1 mask=80 (expected 80) cookie=1950 len=16 name="test_file2" (expected "test") -95
inotify02    7  TPASS  :  get event: wd=1 mask=800 cookie=0 len=0 name="\x01"
inotify02    8  TFAIL  :  get event: wd=1 mask=200 (expected 200) cookie=0 len=16 name="test_file2" (expected "test") -95
inotify02    9  TPASS  :  get event: wd=1 mask=800 cookie=0 len=0 name=""


Thanks,
Wanlong Gao


> 
> Signed-off-by: Garrett Cooper <yanegomi@gmail.com>
> 
> ---
>  testcases/kernel/syscalls/inotify/inotify02.c |   13 ++++---------
>  1 files changed, 4 insertions(+), 9 deletions(-)
> 
> 
> --------------1.7.2.5
> Content-Type: text/x-patch; name="0002-Replace-struct-event_t-with-struct-inotify_event.patch"
> Content-Transfer-Encoding: 8bit
> Content-Disposition: attachment; filename="0002-Replace-struct-event_t-with-struct-inotify_event.patch"
> 
> diff --git a/testcases/kernel/syscalls/inotify/inotify02.c b/testcases/kernel/syscalls/inotify/inotify02.c
> index 59f83ba..c87797f 100644
> --- a/testcases/kernel/syscalls/inotify/inotify02.c
> +++ b/testcases/kernel/syscalls/inotify/inotify02.c
> @@ -81,15 +81,10 @@ char buf[BUF_SIZE];
>  int fd, fd_notify;
>  int wd;
> 
> -struct event_t {
> -    char name[BUF_SIZE];
> -    int mask;
> -    int len;
> -};
>  #define FILE_NAME1 "test_file1"
>  #define FILE_NAME2 "test_file2"
> 
> -struct event_t event_set[EVENT_MAX];
> +struct inotify_event event_set[EVENT_MAX];
> 
>  char event_buf[EVENT_BUF_LEN];
> 
> @@ -239,7 +234,7 @@ int main(int ac, char **av)
>                           "1c17d18e3775485bf1e0ce79575eb637a94494a2.");
>                  tst_resm(TFAIL,
>                       "get unnecessary event: "
> -                     "wd=%d mask=%x cookie=%u len=%u"
> +                     "wd=%d mask=%x cookie=%u len=%u "
>                       "name=\"%s\"", event->wd, event->mask,
>                       event->cookie, event->len,
>                       event->name);
> @@ -250,8 +245,8 @@ int main(int ac, char **av)
>                      (event_set[test_num].name, event->name,
>                       event->len))) {
>                  tst_resm(TPASS,
> -                     "get event: wd=%d mask=%x"
> -                     " cookie=%u len=%u name=\"%s\"",
> +                     "get event: wd=%d mask=%x "
> +                     "cookie=%u len=%u name=\"%s\"",
>                       event->wd, event->mask, event->cookie,
>                       event->len, event->name);
> 
> 
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second 
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> 
> 
> 
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list



------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2012-04-05  1:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  0:42 [LTP] [PATCH 2/2] Replace struct event_t with struct inotify_event Garrett Cooper
2012-04-05  1:39 ` Wanlong Gao [this message]
2012-04-05  2:10   ` Garrett Cooper
2012-04-11  2:53     ` Wanlong Gao
2012-04-11  9:18       ` Garrett Cooper
2012-04-11  9:30         ` Wanlong Gao
2012-05-03 12:46           ` Cyril Hrubis

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=4F7CF7DB.2080802@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=yanegomi@gmail.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