From: Patrick Venture <venture@google.com>
To: laurent@vivier.eu
Cc: qemu-devel@nongnu.org, scw@google.com,
Patrick Venture <venture@google.com>
Subject: [PATCH v3 0/2] linux-user: check read permissions before how
Date: Wed, 26 Jan 2022 13:25:57 -0800 [thread overview]
Message-ID: <20220126212559.1936290-1-venture@google.com> (raw)
In sigprocmask check the read permissions first before checking the `how`.
This is done for both: TARGET_NR_sigprocmask and TARGET_NR_rt_sigprocmask
v3:
* Added missing signature from venture
v2:
* Update code style during code change
* Also update check order for TARGET_NR_sigprocmask
Patrick Venture (1):
linux-user: sigprocmask check read perms first
Shu-Chun Weng (1):
linux-user: rt_sigprocmask, check read perms first
linux-user/syscall.c | 24 ++++++++++++++----------
1 file changed, 14 insertions(+), 10 deletions(-)
--
2.35.0.rc0.227.g00780c9af4-goog
next reply other threads:[~2022-01-26 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 21:25 Patrick Venture [this message]
2022-01-26 21:25 ` [PATCH v3 1/2] linux-user: rt_sigprocmask, check read perms first Patrick Venture
2022-01-27 14:12 ` Laurent Vivier
2022-01-26 21:25 ` [PATCH v3 2/2] linux-user: sigprocmask " Patrick Venture
2022-01-27 14:12 ` Laurent Vivier
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=20220126212559.1936290-1-venture@google.com \
--to=venture@google.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=scw@google.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;
as well as URLs for NNTP newsgroup(s).