From: Ben Hutchings <ben@decadent.org.uk>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kconfig: Avoid buffer underrun in choice input
Date: Fri, 08 Apr 2011 00:41:55 +0100 [thread overview]
Message-ID: <1302219716.5282.8.camel@localhost> (raw)
In-Reply-To: <1300508770.26693.73.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
On Sat, 2011-03-19 at 04:26 +0000, Ben Hutchings wrote:
> commit 40aee729b350672c2550640622416a855e27938f ('kconfig: fix default
> value for choice input') fixed some cases where kconfig would select
> the wrong option from a choice with a single valid option and thus
> enter an infinite loop.
>
> However, this broke the test for user input of the form 'N?', because
> when kconfig selects the single valid option the input is zero-length
> and the test will read the byte before the input buffer. If this
> happens to contain '?' (as it will in a mips build on Debian unstable
> today) then kconfig again enters an infinite loop.
Please acknowledge this and send it upstream.
Ben.
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> Cc: stable@kernel.org [2.6.17+]
> ---
> scripts/kconfig/conf.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/scripts/kconfig/conf.c b/scripts/kconfig/conf.c
> index 659326c..006ad81 100644
> --- a/scripts/kconfig/conf.c
> +++ b/scripts/kconfig/conf.c
> @@ -332,7 +332,7 @@ static int conf_choice(struct menu *menu)
> }
> if (!child)
> continue;
> - if (line[strlen(line) - 1] == '?') {
> + if (line[0] && line[strlen(line) - 1] == '?') {
> print_help(child);
> continue;
> }
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-04-07 23:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 4:26 [PATCH] kconfig: Avoid buffer underrun in choice input Ben Hutchings
2011-04-07 23:41 ` Ben Hutchings [this message]
2011-04-08 11:20 ` Michal Marek
-- strict thread matches above, loose matches on Subject: below --
2011-04-23 17:42 Ben Hutchings
2011-04-23 18:04 ` Sam Ravnborg
2011-04-24 4:02 ` Ben Hutchings
2011-04-24 8:39 ` Geert Uytterhoeven
2011-04-27 11:19 ` Michal Marek
2011-04-27 13:12 ` Ben Hutchings
2011-04-27 17:35 ` Linus Torvalds
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=1302219716.5282.8.camel@localhost \
--to=ben@decadent.org.uk \
--cc=linux-kbuild@vger.kernel.org \
--cc=zippel@linux-m68k.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