From: Richard Palethorpe <rpalethorpe@suse.de>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4 2/3] safe_open, safe_openat: Fix undefined behaviour in vararg handling
Date: Mon, 05 Dec 2022 10:30:05 +0000 [thread overview]
Message-ID: <874juauop3.fsf@suse.de> (raw)
In-Reply-To: <Y4d1/tCohb7fxZkM@yuki>
Hello,
Cyril Hrubis <chrubis@suse.cz> writes:
> Hi!
> Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
>
> --
> Cyril Hrubis
> chrubis@suse.cz
Still not sure I prefer this over the macro approach, but merged,
thanks!
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-12-05 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 15:07 [LTP] [PATCH v4 0/3] safe_macros: Fix undefined behaviour in vararg handling Tudor Cretu
2022-11-30 15:07 ` [LTP] [PATCH v4 1/3] syscalls/f{get, set}xattr: Don't pass a pointer to mode argument in open Tudor Cretu
2022-11-30 15:07 ` [LTP] [PATCH v4 2/3] safe_open, safe_openat: Fix undefined behaviour in vararg handling Tudor Cretu
2022-11-30 15:25 ` Cyril Hrubis
2022-12-05 10:30 ` Richard Palethorpe [this message]
2022-11-30 15:07 ` [LTP] [PATCH v4 3/3] safe_semctl: " Tudor Cretu
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=874juauop3.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=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