reassign 659136 src:linux-2.6 3.1.8-2
forcemerge 659111 659136
quit

Hi Paul,

Paul Menzel wrote:

> Searching for existing reports on the WWW I only found a similar report
> in the RedHat Bugzilla claiming this bug to be fixed in 3.2 which I
> could not try yet.

Please do. You can find 3.2.4-1 in sid; relative to the version you
are currently using, in addition to adding the fix to this, it adds
some fixes to important known security bugs.

Hope that helps,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120208173015.GB6712@burratino">http://lists.debian.org/20120208173015.GB6712@burratino

Dear Jonathan,


Am Mittwoch, den 08.02.2012, 11:30 -0600 schrieb Jonathan Nieder:
> reassign 659136 src:linux-2.6 3.1.8-2
> forcemerge 659111 659136
> quit

> Paul Menzel wrote:
>
> > Searching for existing reports on the WWW I only found a similar report
> > in the RedHat Bugzilla claiming this bug to be fixed in 3.2 which I
> > could not try yet.
>
> Please do. You can find 3.2.4-1 in sid; relative to the version you
> are currently using, in addition to adding the fix to this, it adds
> some fixes to important known security bugs.

I was told that package version 3.2.4-1 which had migrated to
Wheezy/testing [1] fixes this issue.


Thanks,

Paul


[1] http://packages.qa.debian.org/l/linux-2.6.html

fixed 659136 linux-2.6/3.2.4-1
quit

Paul Menzel wrote:

> I was told that package version 3.2.4-1 which had migrated to
> Wheezy/testing [1] fixes this issue.

Thanks for testing.

Sincerely,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120223100254.GA26321@burratino">http://lists.debian.org/20120223100254.GA26321@burratino