From: Joe Perches <joe@perches.com>
To: Nicolas Iooss <nicolas.iooss_linux@m4x.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] printk: fix parsing of "brl=" option
Date: Tue, 23 Aug 2016 09:25:08 -0700 [thread overview]
Message-ID: <1471969508.3746.112.camel@perches.com> (raw)
In-Reply-To: <20160823154735.26294-1-nicolas.iooss_linux@m4x.org>
On Tue, 2016-08-23 at 17:47 +0200, Nicolas Iooss wrote:
> Commit bbeddf52adc1 ("printk: move braille console support into separate
> braille.[ch] files") moved the parsing of braille-related options into
> _braille_console_setup(), changing the type of variable str from char*
> to char**. In this commit, memcmp(str, "brl,", 4) was correctly updated
> to memcmp(*str, "brl,", 4) but not memcmp(str, "brl=", 4).
>
> Update the code to make "brl=" option work again.
>
> Fixes: bbeddf52adc1 ("printk: move braille console support into separate
> braille.[ch] files")
> Signed-off-by: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
> ---
> kernel/printk/braille.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/printk/braille.c b/kernel/printk/braille.c
> index 276762f3a460..f735ade8494c 100644
> --- a/kernel/printk/braille.c
> +++ b/kernel/printk/braille.c
> @@ -12,7 +12,7 @@ char *_braille_console_setup(char **str, char **brl_options)
> if (!memcmp(*str, "brl,", 4)) {
> *brl_options = "";
> *str += 4;
> - } else if (!memcmp(str, "brl=", 4)) {
> + } else if (!memcmp(*str, "brl=", 4)) {
> *brl_options = *str + 4;
> *str = strchr(*brl_options, ',');
> if (!*str)
Thanks.
likely the first memcmp here should be strcmp
and the second should be strncmp
That would have caused the compiler to show
the defect.
next prev parent reply other threads:[~2016-08-23 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 15:47 [PATCH 1/1] printk: fix parsing of "brl=" option Nicolas Iooss
2016-08-23 16:25 ` Joe Perches [this message]
2016-08-23 16:46 ` Nicolas Iooss
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=1471969508.3746.112.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.iooss_linux@m4x.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