linux-kernel - Re: [PATCH resend] hid-magicmouse: Increase evdev buffer size

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] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.1104060617521.5855@pobox.suse.cz>
Date:	Wed, 6 Apr 2011 06:18:13 -0700 (PDT)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Chase Douglas <chase.douglas@...onical.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Jeffrey Brown <jeffbrown@...roid.com>,
	Henrik Rydberg <rydberg@...omail.se>,
	Simon Budig <simon@...ig.de>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH resend] hid-magicmouse: Increase evdev buffer size

On Tue, 5 Apr 2011, Chase Douglas wrote:

> >>>> I'd happuly take Chase's patch, but want to make sure that we don't cause
> >>>> any changes that would make backwards compatilibity an issue later.
> >>>
> >>> There should be no compatibility issues.  However, we might be better
> >>> off in the long term taking (some variation of) these patches instead.
> >>
> >> I like the proposed changes, but I want to ensure stable kernel releases
> >> aren't left out of the fix for hid-magicmouse. I don't know the best way
> >> forward, but here's one possibility:
> >>
> >> 1. Apply my patch to manually set the buffer size hint
> >> 2. It gets sent to stable trees due to the 'Cc: stable@...nel.org' line
> >> 3. Apply Jeffrey's patches, including a reversion of my buffer size hint
> >>
> >> Obviously the extra application and reversion is odd, but this seems the
> >> easiest way forward given that the patches already exist and can be
> >> applied without issue.
> >>
> > 
> > Or, once Jeffrey's patches hit mainline, send your change to stable with
> > the explanation why it is needed for stable but not for mainline.
> 
> One thing that crossed my mind is that Jeffrey's patches wouldn't be
> merged until 2.6.40, right? If so, even 2.6.39 will be released with
> this bug, which makes me want to go with the plan I outlined above.

OK, applied. Thanks everybody.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
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/