From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] syscalls/capget01: Cleanup & convert to new library
Date: Tue, 7 Jan 2020 13:26:04 +0100 [thread overview]
Message-ID: <20200107122604.GC26408@rei.lan> (raw)
In-Reply-To: <20200107120224.GA26408@rei.lan>
Hi!
Also btw, we do not cover the case with pid == 0 now, which should
return the capabilities for the calling thread. I guess that we can run
the capget01 verify function twice, once for pid == getpid() and once
for pid == 0.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-01-07 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 7:25 [LTP] [PATCH 1/2] syscalls/capget01: Cleanup & convert to new library Yang Xu
2019-12-11 7:25 ` [LTP] [PATCH 2/2] syscalls/capget02: " Yang Xu
2020-01-07 12:23 ` Cyril Hrubis
2020-01-07 12:02 ` [LTP] [PATCH 1/2] syscalls/capget01: " Cyril Hrubis
2020-01-07 12:26 ` Cyril Hrubis [this message]
2020-01-08 2:34 ` Yang Xu
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=20200107122604.GC26408@rei.lan \
--to=chrubis@suse.cz \
--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