On Friday 15 February 2013 08:53:28 Bjørn Mork wrote:
> Oliver Neukum writes:
> > We have to let user space recover. To do so we need to indicate when
> > exactly we dropped data.
>
> The problem with that is that this is likely to happen when a client
> just doesn't care. It will just continue
On Thu, Feb 14, 2013 at 02:51:19PM -0800, Ben Widawsky wrote:
> On Thu, Feb 14, 2013 at 07:46:07PM +0100, Daniel Vetter wrote:
> > Yet another remnant ... this might explain why l3 remapping didn't
> > really work on HSW.
> >
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=57441
> > Spo
Oliver Neukum writes:
> On Friday 15 February 2013 08:53:28 Bjørn Mork wrote:
>> Oliver Neukum writes:
>
>> > We have to let user space recover. To do so we need to indicate when
>> > exactly we dropped data.
>>
>> The problem with that is that this is likely to happen when a client
>> just does
On Wed, Feb 13, 2013 at 10:24:05AM -0800, gre...@linuxfoundation.org wrote:
[...]
>
> --- a/drivers/net/xen-netback/netback.c
> +++ b/drivers/net/xen-netback/netback.c
> @@ -143,7 +143,8 @@ void xen_netbk_remove_xenvif(struct xenv
> atomic_dec(&netbk->netfront_count);
> }
>
> -static void
On Fri, 2013-02-15 at 13:19 +, Herton Ronaldo Krzesinski wrote:
> > /* Skip first skb fragment if it is on same page as header fragment. */
> > - start = ((unsigned long)shinfo->frags[0].page == pending_idx);
> > + start = ((unsigned long)shinfo->frags[i].page == pending_idx);
>
> This
Hey,
On Fri, Feb 15, 2013 at 12:47:29PM +1100, Dave Chinner wrote:
> On Thu, Feb 14, 2013 at 12:05:01PM -0800, Greg Kroah-Hartman wrote:
> > On Thu, Feb 14, 2013 at 01:55:12PM -0600, Ben Myers wrote:
> > > > Ok, how about I never apply any xfs stable kernel patch, unless you send
> > > > it to sta
From: Paulo Zanoni
If bit 0 of the features byte (0x18) is set to 0, then, according to
the EDID spec, "the display is non-continuous frequency (multi-mode)
and is only specified to accept the video timing formats that are
listed in Base EDID and certain Extension Blocks".
For more information,
commit ec0c4274e33c0373e476b73e01995c53128f1257 ("futex: Mark
get_robust_list as deprecated") added these two WARN_ONCE calls.
However, WARN_ONCE taints the kernel, and we shouldn't be allowing
any user who wanders by to do this. For example, the system fuzzer
"trinity" uses the tainted state as
On Fri, Feb 15, 2013 at 10:36 AM, Paulo Zanoni wrote:
> From: Paulo Zanoni
>
> If bit 0 of the features byte (0x18) is set to 0, then, according to
> the EDID spec, "the display is non-continuous frequency (multi-mode)
> and is only specified to accept the video timing formats that are
> listed i
On Fri, Feb 15, 2013 at 01:35:00PM +, Ian Campbell wrote:
> On Fri, 2013-02-15 at 13:19 +, Herton Ronaldo Krzesinski wrote:
> > > /* Skip first skb fragment if it is on same page as header fragment. */
> > > - start = ((unsigned long)shinfo->frags[0].page == pending_idx);
> > > + start =
While using a mt9m001 (monochrome) camera the final output falsely gets
horizontally divided into two pictures.
The issue was git bisected to commit f410991dcf1f
| [media] i.MX27 camera: add support for YUV420 format
|
| This patch uses channel 2 of the eMMa-PrP to convert
| format pro
On Fri, Feb 15, 2013 at 06:08:41PM +0100, Christoph Fritz wrote:
> While using a mt9m001 (monochrome) camera the final output falsely gets
> horizontally divided into two pictures.
>
> The issue was git bisected to commit f410991dcf1f
>
> | [media] i.MX27 camera: add support for YUV420 format
On Fri, 2013-02-15 at 13:36 -0200, Paulo Zanoni wrote:
> From: Paulo Zanoni
>
> If bit 0 of the features byte (0x18) is set to 0, then, according to
> the EDID spec, "the display is non-continuous frequency (multi-mode)
> and is only specified to accept the video timing formats that are
> listed
On Thu, Feb 14, 2013 at 09:01:06PM +0100, Thomas Gleixner wrote:
> commit 9ec1882df2 (tty: serial: imx: console write routing is unsafe
> on SMP) introduced a recursive locking bug in imx_console_write().
>
> The callchain is:
>
> imx_rxint()
> spin_lock_irqsave(&sport->port.lock,flags);
> ..
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=53881
Cc: stable@vger.kernel.org
Cc: Jani Nikula
Tested-by: Jani Monoses
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/i915/intel_display.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/
On Fri, Feb 15, 2013 at 06:35:30PM +0100, Daniel Vetter wrote:
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=53881
> Cc: stable@vger.kernel.org
> Cc: Jani Nikula
> Tested-by: Jani Monoses
> Signed-off-by: Daniel Vetter
And merged right away ...
-Daniel
> ---
> drivers/gpu/drm/i915/in
This is a note to let you know that I've just added the patch titled
drivercore: Fix ordering between deferred_probe and exiting initcalls
to my driver-core git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
in the driver-core-next branch.
This is a note to let you know that I've just added the patch titled
TTY: do not update atime/mtime on read/write
to my tty git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
in the tty-next branch.
The patch will show up in the next release of t
CVE-2013-0290
Both 3.4 and 3.7 have the commit that causes this problem.
commit 77c1090f94d1b0b5186fb13a1b71b47b1343f87f
Author: Eric Dumazet
Date: Tue Feb 12 06:16:53 2013 +
net: fix infinite loop in __skb_recv_datagram()
Tommi was fuzzing with trinity and reported the follo
From: Jerry Snitselaar
Date: Fri, 15 Feb 2013 14:04:53 -0700
> CVE-2013-0290
>
> Both 3.4 and 3.7 have the commit that causes this problem.
Can you please not do this?
I queue all networking -stable patches up, as need, and submit them at
a time of my choosing to make sure bug fixes are allowe
On Fri Feb 15 13, David Miller wrote:
> From: Jerry Snitselaar
> Date: Fri, 15 Feb 2013 14:04:53 -0700
>
> > CVE-2013-0290
> >
> > Both 3.4 and 3.7 have the commit that causes this problem.
>
> Can you please not do this?
>
> I queue all networking -stable patches up, as need, and submit them
commit: 249bfb83cf8ba658955f0245ac3981d941f746ee
From: "Rafael J. Wysocki"
Date: Mon, 11 Feb 2013 20:49:49 +0100
Subject: PCI/PM: Clean up PME state when removing a device
Devices are added to pci_pme_list when drivers use pci_enable_wake()
or pci_wake_from_d3(), but they aren't removed from the
commit: 1de63d60cd5b0d33a812efa455d5933bf1564a51
From: Satoru Takeuchi
Date: Thu, 14 Feb 2013 09:12:52 +0900
Subject: efi: Clear EFI_RUNTIME_SERVICES rather than EFI_BOOT by "noefi" boot
parameter
There was a serious problem in samsung-laptop that its platform driver is
designed to run under BIO
This is a note to let you know that I've just added the patch titled
PCI/PM: Clean up PME state when removing a device
to the 3.0-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
pci-pm
This is a note to let you know that I've just added the patch titled
x86/xen: don't assume %ds is usable in xen_iret for 32-bit PVOPS.
to the 3.0-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch
This is a note to let you know that I've just added the patch titled
efi: Clear EFI_RUNTIME_SERVICES rather than EFI_BOOT by "noefi" boot
parameter
to the 3.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filenam
This is a note to let you know that I've just added the patch titled
PCI/PM: Clean up PME state when removing a device
to the 3.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
pci-pm
This is a note to let you know that I've just added the patch titled
x86/xen: don't assume %ds is usable in xen_iret for 32-bit PVOPS.
to the 3.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch
This is a note to let you know that I've just added the patch titled
efi: Clear EFI_RUNTIME_SERVICES rather than EFI_BOOT by "noefi" boot
parameter
to the 3.7-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filenam
This is a note to let you know that I've just added the patch titled
PCI/PM: Clean up PME state when removing a device
to the 3.7-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
pci-pm
This is a note to let you know that I've just added the patch titled
x86/xen: don't assume %ds is usable in xen_iret for 32-bit PVOPS.
to the 3.7-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch
Hi.
I would like to nominate commit
ae1c07a6b7ced6c0c94c99e3b53f4e7856fa8bff for backport to stable
branches earlier than 3.7.
commit ae1c07a6b7ced6c0c94c99e3b53f4e7856fa8bff
Author: Alexander Duyck
Date: Wed Aug 8 05:23:22 2012 +
igb: Remove artificial restriction on RQDPC stat readi
The patch titled
Subject: futex: avoid kernel taint caused by get_robust_list
has been added to the -mm tree. Its filename is
futex-avoid-kernel-taint-caused-by-get_robust_list.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc
Am Fri, 15 Feb 2013 14:26:52 -0800
schrieb a...@linux-foundation.org:
> --
> From: Paul Gortmaker
> Subject: futex: avoid kernel taint caused by get_robust_list
>
> Commit ec0c4274e33c0373e4 ("futex: Mark get_robust_list as
> deprecated") added
This is a note to let you know that I've just added the patch titled
igb: Remove artificial restriction on RQDPC stat reading
to the 3.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
igb: Remove artificial restriction on RQDPC stat reading
to the 3.0-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
On Wed, Feb 13, 2013 at 7:58 AM, Christian Gmeiner
wrote:
> During the development of this driver an in-house register
> documentation was used. The last weeks some integration tests
> were done and this problem was found. It turned out that
> the released register documentation is wrong.
>
> The
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit 0ee364eb316348ddf3e0dfcd986f5f13f528f821 upstream.
A user reported the following oops when a backup process reads
/proc/kcore:
BUG: unable to handle kernel paging request at
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Satoru Takeuchi
commit 1de63d60cd5b0d33a812efa455d5933bf1564a51 upstream.
There was a serious problem in samsung-laptop that its platform driver is
designed to run under BIOS and running under
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 249bfb83cf8ba658955f0245ac3981d941f746ee upstream.
Devices are added to pci_pme_list when drivers use pci_enable_wake()
or pci_wake_from_d3(), but they aren't removed
This is the start of the stable review cycle for the 3.7.9 release.
There are 10 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Feb 17 22:54:03 UTC 2013.
Anything received
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit e575a86fdc50d013bf3ad3aa81d9100e8e6cc60d upstream.
Without this patch, it is trivial to determine kernel page
mappings by examining the error code reported to dmesg[1].
Instead
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit d911e03d097bdc01363df5d81c43f69432eb785c upstream.
Since ed4f209 "s390/time: fix sched_clock() overflow" a new helper function
is used to avoid overflows when converting T
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Gerald Schaefer
commit 9977f0f164d46613288e0b5778eae500dfe06f31 upstream.
With commit 8e72033f2a48 ("thp: make MADV_HUGEPAGE check for
mm->def_flags") the VM_NOHUGEPAGE flag may be set on s390
On Fri, 15 Feb 2013 23:44:44 +0100
Richard Weinberger wrote:
> As stated in [0], I'd simply revert commit ec0c4274 ("futex: Mark
> get_robust_list as deprecated")
Too much talk, not enough patches. I typed it all in again.
--
To unsubscribe from this list: send the line "unsubscribe stable" in
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Beulich
commit 13d2b4d11d69a92574a55bfd985cfb0ca77aebdc upstream.
This fixes CVE-2013-0228 / XSA-42
Drew Jones while working on CVE-2013-0190 found that that unprivileged guest
user
in 32
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit 0ee364eb316348ddf3e0dfcd986f5f13f528f821 upstream.
A user reported the following oops when a backup process reads
/proc/kcore:
BUG: unable to handle kernel paging request at
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Stoney Wang
commit cb214ede7657db458fd0b2a25ea0b28dbf900ebc upstream.
When a HP ProLiant DL980 G7 Server boots a regular kernel,
there will be intermittent lost interrupts which could
result in
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit e575a86fdc50d013bf3ad3aa81d9100e8e6cc60d upstream.
Without this patch, it is trivial to determine kernel page
mappings by examining the error code reported to dmesg[1].
Instead
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stoney Wang
commit cb214ede7657db458fd0b2a25ea0b28dbf900ebc upstream.
When a HP ProLiant DL980 G7 Server boots a regular kernel,
there will be intermittent lost interrupts which could
result in
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Satoru Takeuchi
commit 1de63d60cd5b0d33a812efa455d5933bf1564a51 upstream.
There was a serious problem in samsung-laptop that its platform driver is
designed to run under BIOS and running under
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 3399cfb5df9594495b876d1843a7165f77366b2b upstream.
Commit e7e034e18a0a ("drivers/rtc/rtc-pl031.c: fix the missing operation
on enable") accidentally broke the ST variants o
3.7-stable review patch. If anyone has any objections, please let me know.
--
This reverts commit a56040731e5b00081c6d6c26b99e6e257a5d63d7 which was
commit eb178619f930fa2ba2348de332a1ff1c66a31424 upstream.
It has been reported to cause problems:
http://bugzilla.redhat.c
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Duyck
commit ae1c07a6b7ced6c0c94c99e3b53f4e7856fa8bff upstream.
For some reason the reading of the RQDPC register was being artificially
limited to 4K. Instead of limiting the value
The patch titled
Subject: revert "futex: Mark get_robust_list as deprecated"
has been added to the -mm tree. Its filename is
revert-futex-mark-get_robust_list-as-deprecated.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a su
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Beulich
commit 13d2b4d11d69a92574a55bfd985cfb0ca77aebdc upstream.
This fixes CVE-2013-0228 / XSA-42
Drew Jones while working on CVE-2013-0190 found that that unprivileged guest
user
in 32
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 249bfb83cf8ba658955f0245ac3981d941f746ee upstream.
Devices are added to pci_pme_list when drivers use pci_enable_wake()
or pci_wake_from_d3(), but they aren't removed
This is the start of the stable review cycle for the 3.0.65 release.
There are 4 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Feb 17 22:53:56 UTC 2013.
Anything received
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 249bfb83cf8ba658955f0245ac3981d941f746ee upstream.
Devices are added to pci_pme_list when drivers use pci_enable_wake()
or pci_wake_from_d3(), but they aren't removed
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Duyck
commit ae1c07a6b7ced6c0c94c99e3b53f4e7856fa8bff upstream.
For some reason the reading of the RQDPC register was being artificially
limited to 4K. Instead of limiting the value
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Beulich
commit 13d2b4d11d69a92574a55bfd985cfb0ca77aebdc upstream.
This fixes CVE-2013-0228 / XSA-42
Drew Jones while working on CVE-2013-0190 found that that unprivileged guest
user
in 32
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit d911e03d097bdc01363df5d81c43f69432eb785c upstream.
Since ed4f209 "s390/time: fix sched_clock() overflow" a new helper function
is used to avoid overflows when converting T
This is the start of the stable review cycle for the 3.4.32 release.
There are 8 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Feb 17 22:53:47 UTC 2013.
Anything received
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit 0ee364eb316348ddf3e0dfcd986f5f13f528f821 upstream.
A user reported the following oops when a backup process reads
/proc/kcore:
BUG: unable to handle kernel paging request at
The patch titled
Subject: posix-cpu-timers: fix nanosleep task_struct leak
has been added to the -mm tree. Its filename is
posix-cpu-timers-fix-nanosleep-task_struct-leak.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suit
The patch titled
Subject: futex: avoid kernel taint caused by get_robust_list
has been removed from the -mm tree. Its filename was
futex-avoid-kernel-taint-caused-by-get_robust_list.patch
This patch was dropped because an updated version will be merged
On Fri, Feb 15, 2013 at 11:44:44PM +0100, Richard Weinberger wrote:
> > The ability to deprecate this code has been called into question[1],
> > but if that remains to be finalized, then making this change in the
> > interim seems to make sense.
>
> Do we really want to remove this system call in
67 matches
Mail list logo
