qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH 0/2] linux-user/gen-vdso: minor error handling improvements
Date: Thu, 10 Jul 2025 11:58:10 -0600	[thread overview]
Message-ID: <98ea92b7-d078-4976-8511-d68818270cf6@linaro.org> (raw)
In-Reply-To: <20250710170707.1299926-1-peter.maydell@linaro.org>

On 7/10/25 11:07, Peter Maydell wrote:
> These two small patches improve the error handling in the gen-vdso
> program. Error handling isn't particularly critical here because
> the tool only gets run during the QEMU build process on input
> that we trust (because we generated it by calling a compiler
> for the guest architecture), but these were easy to do.
> 
> The main motivation here is that Coverity complained about not
> checking fseek()'s return value.
> 
> thanks
> -- PMM
> 
> Peter Maydell (2):
>    linux-user/gen-vdso: Handle fseek() failure
>    linux-user/gen-vdso: Don't write off the end of buf[]
> 
>   linux-user/gen-vdso.c | 16 ++++++++++++++--
>   1 file changed, 14 insertions(+), 2 deletions(-)
> 

Queued, thanks.

r~


  parent reply	other threads:[~2025-07-10 18:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10 17:07 [PATCH 0/2] linux-user/gen-vdso: minor error handling improvements Peter Maydell
2025-07-10 17:07 ` [PATCH 1/2] linux-user/gen-vdso: Handle fseek() failure Peter Maydell
2025-07-10 17:43   ` Richard Henderson
2025-07-10 17:07 ` [PATCH 2/2] linux-user/gen-vdso: Don't write off the end of buf[] Peter Maydell
2025-07-10 17:46   ` Richard Henderson
2025-07-10 19:31   ` Peter Maydell
2025-07-10 17:58 ` Richard Henderson [this message]
2025-07-10 19:31   ` [PATCH 0/2] linux-user/gen-vdso: minor error handling improvements Peter Maydell

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=98ea92b7-d078-4976-8511-d68818270cf6@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=laurent@vivier.eu \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).