From: Frazer Leslie Clews <frazer.clews@codethink.co.uk>
To: openembedded-core@lists.openembedded.org
Cc: Frazer Leslie Clews <frazer.clews@codethink.co.uk>
Subject: [PATCH 2/2] fix invalidScanfFormatWidth to prevent overflowing usr_buf
Date: Mon, 28 Oct 2019 17:14:49 +0000 [thread overview]
Message-ID: <20191028171449.8489-3-frazer.clews@codethink.co.uk> (raw)
In-Reply-To: <20191028171449.8489-1-frazer.clews@codethink.co.uk>
Signed-off-by: Frazer Leslie Clews <frazer.clews@codethink.co.uk>
---
meta/recipes-devtools/makedevs/makedevs/makedevs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/makedevs/makedevs/makedevs.c b/meta/recipes-devtools/makedevs/makedevs/makedevs.c
index 01e564afee..32b9872932 100644
--- a/meta/recipes-devtools/makedevs/makedevs/makedevs.c
+++ b/meta/recipes-devtools/makedevs/makedevs/makedevs.c
@@ -360,7 +360,7 @@ static int interpret_table_entry(char *line)
unsigned long mode = 0755, uid = 0, gid = 0, major = 0, minor = 0;
unsigned long start = 0, increment = 1, count = 0;
- if (0 > sscanf(line, "%4095s %c %lo %40s %40s %lu %lu %lu %lu %lu", path,
+ if (0 > sscanf(line, "%4095s %c %lo %39s %39s %lu %lu %lu %lu %lu", path,
&type, &mode, usr_buf, grp_buf, &major, &minor, &start,
&increment, &count))
{
--
2.20.1
next prev parent reply other threads:[~2019-10-28 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 17:14 [PATCH 0/2] Bug fixes for makedevs.c Frazer Leslie Clews
2019-10-28 17:14 ` [PATCH 1/2] fix format strings in makedevs.c in print statements Frazer Leslie Clews
2019-10-28 17:14 ` Frazer Leslie Clews [this message]
2019-10-28 17:32 ` ✗ patchtest: failure for Bug fixes for makedevs.c Patchwork
2019-10-28 19:11 ` [PATCH 0/2] " Andre McCurdy
2019-10-28 21:22 ` Ross Burton
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=20191028171449.8489-3-frazer.clews@codethink.co.uk \
--to=frazer.clews@codethink.co.uk \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.