From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org,
"Alex Bennée" <alex.bennee@linaro.org>,
"Juan Quintela" <quintela@redhat.com>
Subject: [PULL 06/38] qemu-keymap: properly check return from xkb_keymap_mod_get_index
Date: Mon, 3 Jul 2023 14:43:55 +0100 [thread overview]
Message-ID: <20230703134427.1389440-7-alex.bennee@linaro.org> (raw)
In-Reply-To: <20230703134427.1389440-1-alex.bennee@linaro.org>
We can return XKB_MOD_INVALID for AltGr which rightly gets flagged by
sanitisers as an overly wide shift attempt. Properly check the return
type and leave the bitmap as zero in that case. Tested output before
and after is unchanged with the gb and ara keymaps.
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20230630180423.558337-7-alex.bennee@linaro.org>
diff --git a/qemu-keymap.c b/qemu-keymap.c
index 229866e004..8c80f7a4ed 100644
--- a/qemu-keymap.c
+++ b/qemu-keymap.c
@@ -140,6 +140,18 @@ static void usage(FILE *out)
names.options ?: "-");
}
+static xkb_mod_mask_t get_mod(struct xkb_keymap *map, const char *name)
+{
+ xkb_mod_index_t mod;
+ xkb_mod_mask_t mask = 0;
+
+ mod = xkb_keymap_mod_get_index(map, name);
+ if (mod != XKB_MOD_INVALID) {
+ mask = (1 << mod);
+ }
+ return mask;
+}
+
int main(int argc, char *argv[])
{
struct xkb_context *ctx;
@@ -215,14 +227,10 @@ int main(int argc, char *argv[])
mod, xkb_keymap_mod_get_name(map, mod));
}
- mod = xkb_keymap_mod_get_index(map, "Shift");
- shift = (1 << mod);
- mod = xkb_keymap_mod_get_index(map, "Control");
- ctrl = (1 << mod);
- mod = xkb_keymap_mod_get_index(map, "AltGr");
- altgr = (1 << mod);
- mod = xkb_keymap_mod_get_index(map, "NumLock");
- numlock = (1 << mod);
+ shift = get_mod(map, "Shift");
+ ctrl = get_mod(map, "Control");
+ altgr = get_mod(map, "AltGr");
+ numlock = get_mod(map, "NumLock");
state = xkb_state_new(map);
xkb_keymap_key_for_each(map, walk_map, state);
--
2.39.2
next prev parent reply other threads:[~2023-07-03 13:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 13:43 [PULL 00/38] maintainer updates for 8.1: testing, fuzz, plugins, docs, gdbstub Alex Bennée
2023-07-03 13:43 ` [PULL 01/38] gitlab: explicit set artifacts publishing criteria Alex Bennée
2023-07-03 13:43 ` [PULL 02/38] gitlab: ensure coverage job also publishes meson log Alex Bennée
2023-07-03 13:43 ` [PULL 03/38] gitlab: reduce testing scope of check-gcov Alex Bennée
2023-07-03 13:43 ` [PULL 04/38] docs/devel: remind developers to run CI container pipeline when updating images Alex Bennée
2023-07-03 13:43 ` [PULL 05/38] tests/tcg: add mechanism to handle plugin arguments Alex Bennée
2023-07-03 13:43 ` Alex Bennée [this message]
2023-07-03 13:43 ` [PULL 07/38] scripts/oss-fuzz: add a suppression for keymap Alex Bennée
2023-07-03 13:43 ` [PULL 08/38] tests/qtests: clean-up and fix leak in generic_fuzz Alex Bennée
2023-07-03 13:43 ` [PULL 09/38] tests/docker: add test-fuzz Alex Bennée
2023-07-03 13:43 ` [PULL 10/38] Makefile: add lcitool-refresh to UNCHECKED_GOALS Alex Bennée
2023-07-03 13:44 ` [PULL 11/38] tests/lcitool: update to latest version Alex Bennée
2023-07-03 13:44 ` [PULL 12/38] tests/lcitool: Bump fedora container versions Alex Bennée
2023-07-03 13:44 ` [PULL 13/38] tests/lcitool: add an explicit gcc-native package Alex Bennée
2023-07-03 13:44 ` [PULL 14/38] tests/lcitool: introduce qemu-minimal Alex Bennée
2023-07-03 13:44 ` [PULL 15/38] tests/docker: convert riscv64-cross to lcitool Alex Bennée
2023-07-03 13:44 ` [PULL 16/38] tests/avocado: update firmware to enable sbsa-ref/max Alex Bennée
2023-07-03 13:44 ` [PULL 17/38] tests/avocado: Make the test_arm_bpim2u_gmac test more reliable Alex Bennée
2023-07-03 13:44 ` [PULL 18/38] target/arm: make arm_casq_ptw CONFIG_TCG only Alex Bennée
2023-07-03 13:44 ` [PULL 19/38] plugins: force slow path when plugins instrument memory ops Alex Bennée
2023-07-03 13:44 ` [PULL 20/38] plugins: fix memory leak while parsing options Alex Bennée
2023-07-03 13:44 ` [PULL 21/38] plugins: update lockstep to use g_memdup2 Alex Bennée
2023-11-13 10:46 ` Thomas Huth
2023-11-13 11:40 ` Alex Bennée
2023-11-13 11:55 ` Daniel P. Berrangé
2023-11-13 12:21 ` Thomas Huth
2023-07-03 13:44 ` [PULL 22/38] docs/devel: add some front matter to the devel index Alex Bennée
2023-07-03 13:44 ` [PULL 23/38] include/migration: mark vmstate_register() as a legacy function Alex Bennée
2023-07-03 13:44 ` [PULL 24/38] include/hw/qdev-core: fixup kerneldoc annotations Alex Bennée
2023-07-03 13:44 ` [PULL 25/38] docs/devel/qom.rst: Correct code style Alex Bennée
2023-07-03 13:44 ` [PULL 26/38] docs/devel: split qom-api reference into new file Alex Bennée
2023-07-03 13:44 ` [PULL 27/38] docs/devel: introduce some key concepts for QOM development Alex Bennée
2023-07-03 13:44 ` [PULL 28/38] gdbstub: lightly refactor connection to avoid snprintf Alex Bennée
2023-07-03 13:44 ` [PULL 29/38] gdbstub: Permit reverse step/break to provide stop response Alex Bennée
2023-07-08 6:17 ` Michael Tokarev
2023-07-08 10:10 ` Alex Bennée
2023-07-09 8:12 ` Michael Tokarev
2023-07-03 13:44 ` [PULL 30/38] gdbstub: clean-up vcont handling to avoid goto Alex Bennée
2023-07-03 13:44 ` [PULL 31/38] linux-user: Expose do_guest_openat() and do_guest_readlink() Alex Bennée
2023-07-03 13:44 ` [PULL 32/38] linux-user: Add "safe" parameter to do_guest_openat() Alex Bennée
2023-07-03 13:44 ` [PULL 33/38] linux-user: Emulate /proc/self/smaps Alex Bennée
2023-07-03 13:44 ` [PULL 34/38] gdbstub: Expose gdb_get_process() and gdb_get_first_cpu_in_process() Alex Bennée
2023-07-03 13:44 ` [PULL 35/38] gdbstub: Report the actual qemu-user pid Alex Bennée
2023-07-03 13:44 ` [PULL 36/38] gdbstub: Add support for info proc mappings Alex Bennée
2023-07-03 13:44 ` [PULL 37/38] docs: Document security implications of debugging Alex Bennée
2023-07-03 13:44 ` [PULL 38/38] tests/tcg: Add a test for info proc mappings Alex Bennée
2023-07-04 8:19 ` [PULL 00/38] maintainer updates for 8.1: testing, fuzz, plugins, docs, gdbstub Richard Henderson
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=20230703134427.1389440-7-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.henderson@linaro.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).