From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5 1/3] Add SAFE_MPROTECT() macro
Date: Wed, 13 Mar 2024 10:56:19 +0100 [thread overview]
Message-ID: <ZfF4Q7fcBdUCOslR@rei> (raw)
In-Reply-To: <20240313092331.18069-2-andrea.cervesato@suse.de>
Hi!
> +static void prot_to_str(const int prot, char *buf)
> +{
> + char *ptr = buf;
>
I would still put an explicit check for the buffer size here, so that we
are sure that the complete combination of READ|WRITE|EXEC would fit, but
I guess that it's fine as long as this is an internal static function
and not part of the API.
> + if (prot == PROT_NONE) {
> + strcpy(buf, "PROT_NONE");
> + return;
> + }
> +
> + if (prot & PROT_READ) {
> + strcpy(ptr, PROT_FLAG_STR(PROT_READ));
> + ptr += sizeof(PROT_FLAG_STR(PROT_READ)) - 1;
> + }
> +
> + if (prot & PROT_WRITE) {
> + strcpy(ptr, PROT_FLAG_STR(PROT_WRITE));
> + ptr += sizeof(PROT_FLAG_STR(PROT_WRITE)) - 1;
> + }
> +
> + if (prot & PROT_EXEC) {
> + strcpy(ptr, PROT_FLAG_STR(PROT_EXEC));
> + ptr += sizeof(PROT_FLAG_STR(PROT_EXEC)) - 1;
> + }
> +
> + if (buf != ptr)
> + ptr[-3] = 0;
> +}
> +
> static inline void *safe_mmap(const char *file, const int lineno,
> void *addr, size_t length,
> int prot, int flags, int fd, off_t offset)
> @@ -287,6 +318,35 @@ static inline void *safe_mmap(const char *file, const int lineno,
> safe_mmap(__FILE__, __LINE__, (addr), (length), (prot), \
> (flags), (fd), (offset))
>
> +static inline int safe_mprotect(const char *file, const int lineno,
> + char *addr, size_t len, int prot)
> +{
> + int rval;
> + char *prot_buf;
> +
> + prot_buf = (char*) safe_malloc(file, lineno, 0, 512);
Why are we allocating the buffer? Why not just prot_buf[512] ?
Also the cast to (char*) is never needed in C as void* is automatically
converted to any type of a pointer without explicit cast.
Otherwise it looks good. You can add my Reviewed-by: if you change the
malloc to an array on the stack.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-03-13 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 9:23 [LTP] [PATCH v5 0/3] SysV IPC bug reproducer Andrea Cervesato
2024-03-13 9:23 ` [LTP] [PATCH v5 1/3] Add SAFE_MPROTECT() macro Andrea Cervesato
2024-03-13 9:56 ` Cyril Hrubis [this message]
2024-03-13 9:59 ` Cyril Hrubis
2024-03-13 9:23 ` [LTP] [PATCH v5 2/3] Print prot flag when SAFE_MMAP() fails Andrea Cervesato
2024-03-13 9:57 ` Cyril Hrubis
2024-03-13 9:23 ` [LTP] [PATCH v5 3/3] Add shmat04 SysV IPC bug reproducer Andrea Cervesato
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=ZfF4Q7fcBdUCOslR@rei \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.de \
--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