All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhaogongyi via ltp <ltp@lists.linux.it>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] futex_waitv04: Add test for futex_waitv syscall
Date: Fri, 15 Apr 2022 01:27:35 +0000	[thread overview]
Message-ID: <c9aee645b8c146aa9b87b2cb26a6dfd1@huawei.com> (raw)

Hi Cyril,

I also wondered whether to add these two testcases into futex_waitv01.c, there is a consideration that there are alse two other testcases need to be added according to linux manual:

1. A signal was sent to the sleeping task, returning -ERESTARTSYS.
2. Some futex at the list was woken, returning the index of some waked futex.

Best wishes!

Gongyi

> Hi!
> > diff --git a/testcases/kernel/syscalls/futex/futex_waitv04.c
> > b/testcases/kernel/syscalls/futex/futex_waitv04.c
> > new file mode 100644
> > index 000000000..783d481e9
> > --- /dev/null
> > +++ b/testcases/kernel/syscalls/futex/futex_waitv04.c
> > @@ -0,0 +1,83 @@
> > +// SPDX-License-Identifier: GPL-2.0-or-later
> > +/*
> > + * Copyright (C) 2022 Zhao Gongyi <zhaogongyi@huawei.com>  */
> > +
> > +/*\
> > + * [Description]
> > + *
> > + * This test verifies EAGIN and ETIMEDOUT for futex_waitv syscall.
>                          ^
>                          EAGAIN
> 
> Is there a reason why can't we add these two testcases into
> futex_waitv01.c?
> 
> --
> Cyril Hrubis
> chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2022-04-15  1:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15  1:27 zhaogongyi via ltp [this message]
2022-06-06 14:35 ` [LTP] [PATCH] futex_waitv04: Add test for futex_waitv syscall Cyril Hrubis
  -- strict thread matches above, loose matches on Subject: below --
2022-06-07  2:58 zhaogongyi via ltp
2022-04-13 11:40 Zhao Gongyi via ltp
2022-04-14 13: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=c9aee645b8c146aa9b87b2cb26a6dfd1@huawei.com \
    --to=ltp@lists.linux.it \
    --cc=chrubis@suse.cz \
    --cc=zhaogongyi@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.