linux-kernel - Re: [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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101219080427.GA10074@core.coreip.homeip.net>
Date:	Sun, 19 Dec 2010 00:04:28 -0800
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Henrik Rydberg <rydberg@...omail.se>
Cc:	Jiri Kosina <jkosina@...e.cz>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [PATCH] Input: Fix double equality sign in uevent

On Sat, Dec 18, 2010 at 08:31:57PM +0100, Henrik Rydberg wrote:
> 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.
> 

Hmm, I do not think so because:

- either nobody uses bitmap variables and then it is not priority
- users worked around the problem and by applying fix we'd be
  breaking their setups.

I think we should apply it but at the beginning of .38 cycle to give us
a chance to evaluate and maybe revert.

Does this make sense?

-- 
Dmitry
--
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/