From: Lucas De Marchi <lucas.demarchi@intel.com>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: <linux-modules@vger.kernel.org>
Subject: Re: [PATCH 1/2] depmod: Fix writing over array length
Date: Mon, 27 Jun 2022 09:42:58 -0700 [thread overview]
Message-ID: <20220627164258.5hi53js77znemrwb@ldmartin-desk2> (raw)
In-Reply-To: <20220603204902.4295-1-lucas.de.marchi@gmail.com>
These 2 patches are now applied.
Lucas De Marchi
On Fri, Jun 03, 2022 at 01:49:01PM -0700, Lucas De Marchi wrote:
>Make sure return value in flush_stream_to() is the length written
>if the value didn't the size. Fix warning on gcc 12.1:
>
> tools/depmod.c: In function ‘output_builtin_alias_bin’:
> tools/depmod.c:2465:24: warning: array subscript 4096 is above array bounds of ‘char[4096]’ [-Warray-bounds]
> 2465 | modname[len] = '\0';
> | ~~~~~~~^~~~~
> tools/depmod.c:2460:22: note: while referencing ‘modname’
> 2460 | char modname[PATH_MAX];
> | ^~~~~~~
> tools/depmod.c:2477:22: warning: array subscript 4096 is above array bounds of ‘char[4096]’ [-Warray-bounds]
> 2477 | value[len] = '\0';
> | ~~~~~^~~~~
> tools/depmod.c:2461:22: note: while referencing ‘value’
> 2461 | char value[PATH_MAX];
> | ^~~~~
>
>Signed-off-by: Lucas De Marchi <lucas.de.marchi@gmail.com>
>---
> tools/depmod.c | 1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/tools/depmod.c b/tools/depmod.c
>index 4117dd1..364b7d4 100644
>--- a/tools/depmod.c
>+++ b/tools/depmod.c
>@@ -2430,6 +2430,7 @@ static int flush_stream_to(FILE *in, int endchar, char *dst, size_t dst_sz)
> if (i == dst_sz) {
> WRN("Could not flush stream: %d. Partial content: %.*s\n",
> ENOSPC, (int) dst_sz, dst);
>+ i--;
> }
>
> return c == endchar ? i : 0;
>--
>2.36.1
>
prev parent reply other threads:[~2022-06-27 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 20:49 [PATCH 1/2] depmod: Fix writing over array length Lucas De Marchi
2022-06-03 20:49 ` [PATCH 2/2] modprobe: re-use modname variable Lucas De Marchi
2022-06-27 16:42 ` Lucas De Marchi [this message]
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=20220627164258.5hi53js77znemrwb@ldmartin-desk2 \
--to=lucas.demarchi@intel.com \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.de.marchi@gmail.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