Bug#852324: [Xen-devel] Bug#852324: x86/mm: Found insecure W+X mapping

2017-03-16 Thread Boris Ostrovsky
On 03/16/2017 08:18 PM, Ben Hutchings wrote: On Thu, 2017-03-16 at 21:49 +, Andrew Cooper wrote: On 16/03/2017 21:05, Ben Hutchings wrote: On Thu, 2017-03-16 at 00:50 +, Ben Hutchings wrote: On Wed, 2017-03-15 at 22:24 +, Ben Hutchings wrote: Control: retitle -1 [xen] x86/mm: Fo

Bug#857997: firmware-misc-nonfree: Include Intel Kabylake GuC 9.14 and Broxton GuC 8.7

2017-03-16 Thread Ben Caradoc-Davies
Package: firmware-misc-nonfree Version: 20161130-2 Severity: normal Dear Maintainer, update-initramfs reports missing i915 firmware: Processing triggers for initramfs-tools (0.127) ... update-initramfs: Generating /boot/initrd.img-4.9.0-2-amd64 W: Possible missing firmware /lib/firmware/i915/kbl

Bug#852324: [Xen-devel] Bug#852324: x86/mm: Found insecure W+X mapping

2017-03-16 Thread Ben Hutchings
On Thu, 2017-03-16 at 21:49 +, Andrew Cooper wrote: > On 16/03/2017 21:05, Ben Hutchings wrote: > > On Thu, 2017-03-16 at 00:50 +, Ben Hutchings wrote: > > > On Wed, 2017-03-15 at 22:24 +, Ben Hutchings wrote: > > > > Control: retitle -1 [xen] x86/mm: Found insecure W+X mapping > > > >

Bug#852324: [Xen-devel] Bug#852324: x86/mm: Found insecure W+X mapping

2017-03-16 Thread Andrew Cooper
On 16/03/2017 21:05, Ben Hutchings wrote: > On Thu, 2017-03-16 at 00:50 +, Ben Hutchings wrote: >> On Wed, 2017-03-15 at 22:24 +, Ben Hutchings wrote: >>> Control: retitle -1 [xen] x86/mm: Found insecure W+X mapping >>> Control: tag -1 upstream confirmed >>> Control: found -1 4.9.13-1 >>> >

Bug#852324: x86/mm: Found insecure W+X mapping

2017-03-16 Thread Ben Hutchings
On Thu, 2017-03-16 at 00:50 +, Ben Hutchings wrote: > On Wed, 2017-03-15 at 22:24 +, Ben Hutchings wrote: > > Control: retitle -1 [xen] x86/mm: Found insecure W+X mapping > > Control: tag -1 upstream confirmed > > Control: found -1 4.9.13-1 > > > > I can reproduce this with a current Debia

Bug#857916: linux-image-4.9.0-2-amd64: btrfs modifying wrong mount point data upon new mount

2017-03-16 Thread Philipp Marek
Hi Ben, thank you for the quick answer! > btrfs includes its own logical volume management and can spread a > filesystem across multiple devices, so in general it has to use UUIDs > to find the devices for a filesytem. Still it shouldn't change the block device name for a mounted filesystem. >

Processed: Re: Bug#857916: linux-image-4.9.0-2-amd64: btrfs modifying wrong mount point data upon new mount

2017-03-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 upstream Bug #857916 [src:linux] linux-image-4.9.0-2-amd64: btrfs modifying wrong mount point data upon new mount Added tag(s) upstream. -- 857916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857916 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#857916: linux-image-4.9.0-2-amd64: btrfs modifying wrong mount point data upon new mount

2017-03-16 Thread Ben Hutchings
Control: tag -1 upstream On Thu, 2017-03-16 at 11:49 +0100, Philipp Marek wrote: > Package: src:linux > Version: 4.9.13-1 > Severity: normal > > I'm using DRBD to keep a backup of my root filesystem (multiple snapshots  > on remote machine). > > Now I wanted to access an old version of a file; s

Bug#810014: I get this too

2017-03-16 Thread Dick Middleton
Same OS: Package: linux-image-3.16.0-4-amd64 I'm also using EATON ups Dick -- Dick Middleton d...@fouter.net

Bug#857916: linux-image-4.9.0-2-amd64: btrfs modifying wrong mount point data upon new mount

2017-03-16 Thread Philipp Marek
Package: src:linux Version: 4.9.13-1 Severity: normal I'm using DRBD to keep a backup of my root filesystem (multiple snapshots on remote machine). Now I wanted to access an old version of a file; so I got me access to the right snapshot (again via DRBD), and tried to mount the filesystem. Fir

Bug#857912: rpc-svcgssd.service: references wrong environment variable

2017-03-16 Thread Rob Leslie
Package: nfs-common Version: 1:1.3.4-2 Severity: normal File: /lib/systemd/system/rpc-svcgssd.service Tags: patch Dear Maintainer, The /usr/lib/systemd/scripts/nfs-utils_env.sh script prepares an environment variable RPCSVCGSSDARGS from $RPCSVCGSSDOPTS (set in /etc/default/nfs-common), however th

AW: Bug#854854: qcontrol: reboot/poweroff

2017-03-16 Thread Peter Buechner
Hello, I cleared the bug according the link below and the system is working now . But what I wonder: my kernel version is 3.16.0-4-kirkwood. How I got this? I followed the procedure on page http://www.cyrius.com/debian/kirkwood/qnap/ts-119/deinstall/ And got the kernel and initrd files of the i

Re: AW: Bug#854854: qcontrol: reboot/poweroff

2017-03-16 Thread Uwe Kleine-König
Hello Peter, On 03/16/2017 10:52 AM, Peter Buechner wrote: > I cleared the bug according the link below and the system is working now . \o/ > But what I wonder: my kernel version is 3.16.0-4-kirkwood. How I got this? This is expected for a jessie system. > I followed the procedure on page > h

Re: Bug#854854: qcontrol: reboot/poweroff

2017-03-16 Thread Uwe Kleine-König
Cc += Alexandre Belloni, debian-kernel, stable@k.o Hello, On Wed, Mar 15, 2017 at 06:10:47PM -0700, Martin Michlmayr wrote: > > After new installation of Debian the system is properly powering > > down either shutdownor by power button. Also the restart is working > > by power button. But after s