Hi
I've noticed that linux-image-amd64 still depends on kernel
3.16-0.bpo.3. Because of this the latest kernel is not installed
automatically on dist-upgrade, thus many systems (ex. on gcloud) still
run the previous version (3.16.5~).
Thanks
--
To UNSUBSCRIBE, email to debian-kernel-requ...@li
On Sat, 2014-12-06 at 23:42 +, Martin Zobel-Helas wrote:
> Package: src:linux
> Version: 3.16.7-2
> Severity: normal
> Tags: patch
>
> Hi,
>
> i have very bad disk IO performance on my MacBook Pro 11.2 with a
> Samsung PCIe SSD. This seems to be kernel issue
> https://bugzilla.kernel.org/show
On Mon, 2014-12-08 at 02:25 +, Ben Hutchings wrote:
> I'm intending to upload linux version 3.16.7-ckt2-1 to sid tomorrow.
[...]
That means: some time after 12:00 UTC on Monday.
Ben.
--
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.
signature.asc
Descrip
I'm intending to upload linux version 3.16.7-ckt2-1 to sid tomorrow.
This includes:
- Stable updates 3.16.7-ckt{1,2} with many important fixes
- Improved support for various ARM/ARM64 machines
- Proper Thunderbolt support on Apple hardware (really, this time)
- Various security fixes
There is no
On Sun, Dec 07, 2014 at 08:53:56PM +, Ben Hutchings wrote:
> > > I found a number of missing patches and incorrect cherry-picks, which
> > > these patches should fix.
> >
> > Wow, much appreciated, thank you! Do you want them in the next release ?
> > I can add them to the current review and i
Processing control commands:
> tag -1 security
Bug #772508 [src:linux] linux: mitigate offset2lib ASLR issue
Added tag(s) security.
> forwarded -1 https://lkml.org/lkml/2014/12/5/482
Bug #772508 [src:linux] linux: mitigate offset2lib ASLR issue
Set Bug forwarded-to-address to 'https://lkml.org/lkm
package: src:linux
severity: important
version: 3.16.7-1
control: tag -1 security
control: forwarded -1 https://lkml.org/lkml/2014/12/5/482
A fix is currently being developed for an an ASLR bypass issue (see
link). Please consider applying and enabling it by default for jessie
kernels once a fina
I think you want these too:
af726f21ed8a x86_64, traps: Fix the espfix64 #DF fixup and rewrite it in C
b645af2d5905 x86_64, traps: Rework bad_iret
I'm attaching backports to 3.2.
Ben.
--
Ben Hutchings
Experience is directly proportional to the value of equipment destroyed.
Hi Ben,
On Sun, Dec 07, 2014 at 07:48:58PM +, Ben Hutchings wrote:
> I've belatedly reviewed stable updates 2.6.32.61-2.6.32.64 for the
> Debian 6 (squeeze) LTS project. We haven't yet included those in a
> update for Debian 6, although we do have most of the security fixes.
>
> I found a nu
On Sun, 2014-12-07 at 21:42 +0100, Willy Tarreau wrote:
> Hi Ben,
>
> On Sun, Dec 07, 2014 at 07:48:58PM +, Ben Hutchings wrote:
> > I've belatedly reviewed stable updates 2.6.32.61-2.6.32.64 for the
> > Debian 6 (squeeze) LTS project. We haven't yet included those in a
> > update for Debian
On 7 December 2014 at 20:57, Ben Hutchings wrote:
> Upstream commit e727ca82e0e9 ("proc connector: fix info leaks")
> changed many functions that don't exist in 2.6.32.y. When it was
> cherry-picked into 2.6.32.61, one extra memset() calls was inserted
> into proc_exit_connector(). This results
Upstream commit 9c4bdf697c39 ("md/raid6: avoid data corruption during
recovery of double-degraded RAID6") changes handle_stripe(), but we
have separate functions for RAID5 and RAID6 and need to apply the
change to handle_stripe6(). When cherry-picked, the change was
wrongly applied to handle_strip
One deletion was omitted from the backport of upstream commit c485658bae87
("net: sctp: fix skb leakage in COOKIE ECHO path of chunk->auth_chunk").
Signed-off-by: Ben Hutchings
---
net/sctp/sm_statefuns.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/net/sctp/sm_statefuns.c b/net/sctp/sm_st
From: Matthijs Kooijman
commit deede2fabe24e00bd7e246eb81cd5767dc6fcfc7 upstream.
When (de)configuring a vlan interface, the IFF_ALLMULTI ans IFF_PROMISC
flags are cleared or set on the underlying interface. So, if these flags
are changed on a vlan interface that is not up, the flags underlying
Upstream commit e727ca82e0e9 ("proc connector: fix info leaks")
changed many functions that don't exist in 2.6.32.y. When it was
cherry-picked into 2.6.32.61, one extra memset() calls was inserted
into proc_exit_connector(). This results in clearing the cpu
field of exit events.
Signed-off-by: B
Upstream commit 58f09e00ae09 was applied to the wrong function when
cherry-picked for 2.6.32.61.
Signed-off-by: Ben Hutchings
---
drivers/block/cciss.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c
index b2225ab..d4d165a 100644
From: Muthukumar Ratty
commit e81ca6fe85b77109a32489a5db82f575d51dfc98 upstream.
If the queue is dead blk_execute_rq_nowait() doesn't invoke the done()
callback function. That will result in blk_execute_rq() being stuck
in wait_for_completion(). Avoid this by initializing rq->end_io to the
done(
From: Tejun Heo
commit 8ba61435d73f2274e12d4d823fde06735e8f6a54 upstream.
blk_insert_cloned_request(), blk_execute_rq_nowait() and
blk_flush_plug_list() either didn't check whether the queue was dead
or did it without holding queue_lock. Update them so that dead state
is checked while holding q
From: Muthukumar Ratty
commit e81ca6fe85b77109a32489a5db82f575d51dfc98 upstream.
If the queue is dead blk_execute_rq_nowait() doesn't invoke the done()
callback function. That will result in blk_execute_rq() being stuck
in wait_for_completion(). Avoid this by initializing rq->end_io to the
done(
From: Tejun Heo
commit 8ba61435d73f2274e12d4d823fde06735e8f6a54 upstream.
blk_insert_cloned_request(), blk_execute_rq_nowait() and
blk_flush_plug_list() either didn't check whether the queue was dead
or did it without holding queue_lock. Update them so that dead state
is checked while holding q
I've belatedly reviewed stable updates 2.6.32.61-2.6.32.64 for the
Debian 6 (squeeze) LTS project. We haven't yet included those in a
update for Debian 6, although we do have most of the security fixes.
I found a number of missing patches and incorrect cherry-picks, which
these patches should fix
Package: src:linux
Version: 3.16.5-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
i am using my thinkpad like everytime befor with closing the lid
and going into stanby, opening up and waking up.
but now ive got some problems with it
ineffective)?
I am n
On Sat, 25 Oct 2014 19:35:45 +, Camaleón wrote:
(...)
> Recently, (since October 8 and not before) some of my servers running an
> up-to-date Wheezy with aacraid card (Adaptec 2020SA) are going nuts:
>
> (...)
> Oct 12 07:38:34 my_machine kernel: [3007914.062687] aacraid: Host
> adapter abo
On 2014-12-07, Ian Campbell wrote:
> On Sun, 2014-12-07 at 11:15 +0100, Uwe Kleine-König wrote:
>> On Sat, Dec 06, 2014 at 12:24:55AM +, peter green wrote:
...
>> > Currently i'm aware of three ways of building deb packaged kernels.
>> >
>> > 1: modify the Debian "linux" source package
>> > 2
I found that the kernel option
video.use_native_backlight=0
fixes these issues. Brightness is always at a reasonable level and
adjustable again. (In fact unfortunately it can't be dimmed to black
anymore, which on the upside avoids unreasonable defaults.)
Tested for Linux 3.16 and 3.17.
$ ls /sy
On Sun, 2014-12-07 at 11:15 +0100, Uwe Kleine-König wrote:
> Hello,
>
> On Sat, Dec 06, 2014 at 12:24:55AM +, peter green wrote:
> > Currently the raspberry pi foundation build their kernel and
> > firmware into the same package in a way that does not work with dkms
> > or generally integrate
Hello,
On Sat, Dec 06, 2014 at 12:24:55AM +, peter green wrote:
> Currently the raspberry pi foundation build their kernel and
> firmware into the same package in a way that does not work with dkms
> or generally integrate with Debian stuff. I've recently been talking
> to shiftplusone (who wo
27 matches
Mail list logo
