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:59:00 +0100 [thread overview]
Message-ID: <ZfF45PrePj-RujiR@rei> (raw)
In-Reply-To: <20240313092331.18069-2-andrea.cervesato@suse.de>
Hi!
> +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);
> + prot_to_str(prot, prot_buf);
> +
> + tst_res_(file, lineno, TDEBUG,
> + "mprotect(%p, %ld, %s(%x))", addr, len, prot_buf, prot);
> +
> + free(prot_buf);
> +
> + rval = mprotect(addr, len, prot);
> +
> + if (rval == -1) {
> + tst_brk_(file, lineno, TBROK | TERRNO,
> + "mprotect() failed");
> + } else if (rval) {
> + tst_brk_(file, lineno, TBROK | TERRNO,
> + "Invalid mprotect() return value %d", rval);
> + }
Ah, and can we please print the whole parameter list for mprotect() in
these two cases as well?
> + return rval;
> +}
> +#define SAFE_MPROTECT(addr, len, prot) \
> + safe_mprotect(__FILE__, __LINE__, (addr), (len), (prot))
> +
> static inline int safe_ftruncate(const char *file, const int lineno,
> int fd, off_t length)
> {
> --
> 2.35.3
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-03-13 10:01 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
2024-03-13 9:59 ` Cyril Hrubis [this message]
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=ZfF45PrePj-RujiR@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