From: Li Qiang <liq3ea@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] keymaps: detect recursive keyboard layout file
Date: Thu, 15 Nov 2018 18:22:15 +0800 [thread overview]
Message-ID: <CAKXe6SLc20J3daRdVaVHBf5WC1=sK1ewHFxxNxP86ToVNjFbRw@mail.gmail.com> (raw)
In-Reply-To: <20181115101513.r4vz4p5gwduhwp4n@sirius.home.kraxel.org>
Gerd Hoffmann <kraxel@redhat.com> 于2018年11月15日周四 下午6:15写道:
> On Thu, Nov 15, 2018 at 01:04:23AM -0800, Li Qiang wrote:
> > When the parse_keyboard_layout() find a "include " line
> > in the keyboard layout file, it will call parse_keyboard_layout()
> > to perform a recursive parse. If the keyboard layout is malformed
> > by adding a line include itself, this can cause an infinite parse.
> > Thus cause qemu a segv. This patch avoid this.
>
> Hmm. Most keymap files are generated by qemu-keymap these days and do
> not use includes in the first place. Three are left over: nl-be, sl,
> sv.
>
> Looking at them it seems like nl-be is not functional, it just includes
> "common" and doesn't define any mappings. For sl and sv I have no clue
> what keymap they represent.
>
> So I'd suggest to just remove support for "include", drop the nl-be map,
> fix the sl and sv maps that they don't need "include" any more. Either
> just replace the "include" statement with the content of the "common"
> file. Or, if someone has a clue what keyboard layout these keymaps are
> for, add rules to the Makefile and update them using then using
> qemu-keymap.
>
Hello Gerd,
Thanks for your advice.
Here my consideration is for the '-k' option can specific any file.
Though it seems too radical, I consider every input can't be trusted.
Anyway, it's ok you ingore this patch.
Thanks,
Li Qiang
>
> cheers,
> Gerd
>
>
next prev parent reply other threads:[~2018-11-15 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 9:04 [Qemu-devel] [PATCH] keymaps: detect recursive keyboard layout file Li Qiang
2018-11-15 10:15 ` Gerd Hoffmann
2018-11-15 10:22 ` Li Qiang [this message]
2018-11-15 13:29 ` Markus Armbruster
2018-11-16 3:14 ` Li Qiang
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='CAKXe6SLc20J3daRdVaVHBf5WC1=sK1ewHFxxNxP86ToVNjFbRw@mail.gmail.com' \
--to=liq3ea@gmail.com \
--cc=kraxel@redhat.com \
--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).