linux-kernel - [PATCH] Input: Fix double equality sign in uevent

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1292700717-1610-1-git-send-email-rydberg@euromail.se>
Date:	Sat, 18 Dec 2010 20:31:57 +0100
From:	"Henrik Rydberg" <rydberg@...omail.se>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Jiri Kosina <jkosina@...e.cz>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org, Henrik Rydberg <rydberg@...omail.se>,
	stable@...nel.org
Subject: [PATCH] Input: Fix double equality sign in uevent

Looking at the uevent stream for input devices, all properties
are on the form "A=B" except the bitmap values, which are on the
form "A==B". Remedied with this patch.

Cc: stable@...nel.org
Signed-off-by: Henrik Rydberg <rydberg@...omail.se>
---
Hi Dmitry,

Unless the input bitmap properties should really behave differently,
this patch ought to be a candidate for 2.6.37.

Thanks,
Henrik

 drivers/input/input.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/input/input.c b/drivers/input/input.c
index c3e5fc7..bed725f 100644
--- a/drivers/input/input.c
+++ b/drivers/input/input.c
@@ -1471,7 +1471,7 @@ static int input_add_uevent_bm_var(struct kobj_uevent_env *env,
 {
 	int len;
 
-	if (add_uevent_var(env, "%s=", name))
+	if (add_uevent_var(env, "%s", name))
 		return -ENOMEM;
 
 	len = input_print_bitmap(&env->buf[env->buflen - 1],
-- 
1.7.2.3

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/