public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Caspar Zhang <caspar@linux.alibaba.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 1/2] syscalls/cma: test case should return TCONF if syscall doesn't exist
Date: Sat, 23 Feb 2019 14:21:35 +0800	[thread overview]
Message-ID: <20190223062135.GB49700@linux.alibaba.com> (raw)
In-Reply-To: <255283985.2485664.1550860167075.JavaMail.zimbra@redhat.com>

On Fri, Feb 22, 2019 at 01:29:27PM -0500, Jan Stancek wrote:
>
>
> ----- Original Message -----
[snip]
> > > > diff --git a/testcases/kernel/syscalls/cma/process_vm_readv03.c
> > > > b/testcases/kernel/syscalls/cma/process_vm_readv03.c
> > > > index 45f7c92e499c..1cec442b3456 100644
> > > > --- a/testcases/kernel/syscalls/cma/process_vm_readv03.c
> > > > +++ b/testcases/kernel/syscalls/cma/process_vm_readv03.c
> > > > @@ -181,7 +181,7 @@ static long *fetch_remote_addrs(void)
> > > >         remote.iov_len = len;
> > > >
> > > >         TEST(ltp_syscall(__NR_process_vm_readv, pids[0], &local,
> > > > -                        1, &remote, 1, 0));
> > > > +                        1, &remote, 1, 0L));
> > > >
> > >
> > > To make things more safely, probably we'd better change all the integer
> > > parameter too?
> > >
> > > -                        1, &remote, 1, 0));
> > > +                        1L, &remote, 1L, 0L));
> >
> > Agreed, let's match all parameters types as before commit:
> >  9b02cd465f70 ("syscalls/cma: test case should return TCONF if syscall
> >  doesn't exist")
>
> So, it looks like this thread has stalled. I'll look into posting a patch,
> unless I hear someone is already working on it.

Hi Jan,

Jason told me he was looking into it, I'll double confirm with him about
the progress. Will update ASAP.

Thanks,
Caspar

  reply	other threads:[~2019-02-23  6:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03  9:43 [LTP] [PATCH] syscalls/cma: test case should return TCONF if syscall doesn't exist Jason Xing
2018-12-03  9:58 ` Jan Stancek
2018-12-04  2:49   ` Jason Xing
2018-12-04  8:54     ` Jan Stancek
2018-12-05 13:43       ` [LTP] [PATCH v2 1/2] " Jason Xing
2018-12-05 13:43         ` [LTP] [PATCH v2 2/2] lapi/syscalls: Add syscall numbers for process_vm_readv/_writev Jason Xing
2018-12-05 22:07           ` Petr Vorel
2018-12-06  3:37             ` Jason Xing
2019-02-15 10:50         ` [LTP] [PATCH v2 1/2] syscalls/cma: test case should return TCONF if syscall doesn't exist Li Wang
2019-02-15 13:53           ` Jan Stancek
2019-02-16  7:18             ` Li Wang
2019-02-16 10:28               ` Jan Stancek
2019-02-22 18:29                 ` Jan Stancek
2019-02-23  6:21                   ` Caspar Zhang [this message]
2019-02-25  8:22                     ` [LTP] [PATCH] syscalls/cma: fix the failure of compiling with O2 option Jason Xing
2019-02-25 10:34                       ` Li Wang
2019-02-25 10:47                       ` Jan Stancek
2019-02-25 13:16                         ` Caspar Zhang
2019-02-26  1:42                           ` [LTP] [PATCH v2] " Jason Xing
2019-02-26  2:22                             ` [LTP] [PATCH v3] " Jason Xing
2019-02-26  3:17                               ` Li Wang
2019-02-26 16:03                               ` Jan Stancek
2019-02-26  2:00                         ` [LTP] [PATCH] " Jason Xing

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=20190223062135.GB49700@linux.alibaba.com \
    --to=caspar@linux.alibaba.com \
    --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