Re: Kernel 3.0.X Linux kernel race condition with PTRACE_SETREGS CVE-2013-0871

2013-02-20 Thread Stefan Priebe - Profihost AG
Am 21.02.2013 00:35, schrieb Ben Hutchings: > On Wed, 2013-02-20 at 17:29 +0100, Oleg Nesterov wrote: >> Hi Ben, >> >> sorry for delay, >> >> On 02/20, Ben Hutchings wrote: >>> >>> On Tue, 2013-02-19 at 20:35 +0100, Stefan Priebe wrote: Am 19.02.2013 20:05, schrieb Ben Hutchings: > On Tue

Patch Upstream: p54usb: corrected USB ID for T-Com Sinus 154 data II

2013-02-20 Thread Gregs git-bot
commit: 008e33f733ca51acb2dd9d88ea878693b04d1d2a From: Tomasz Guszkowski Date: Tue, 5 Feb 2013 22:10:31 +0100 Subject: p54usb: corrected USB ID for T-Com Sinus 154 data II Corrected USB ID for T-Com Sinus 154 data II. ISL3887-based. The device was tested in managed mode with no security, WEP 128

Patch Upstream: rtlwifi: rtl8192cu: Add new USB ID

2013-02-20 Thread Gregs git-bot
commit: 8708aac79e4572ba673d7a21e94ddca9f3abb7fc From: Larry Finger Date: Fri, 8 Feb 2013 12:28:18 -0600 Subject: rtlwifi: rtl8192cu: Add new USB ID A new model of the RTL8188CUS has appeared. Reported-and-tested-by: Thomas Rosenkrantz Signed-off-by: Larry Finger Cc: Stable Signed-off-by: Joh

Patch Upstream: rtlwifi: rtl8192cu: Fix NULL dereference BUG when using new_id

2013-02-20 Thread Gregs git-bot
commit: 957f4aca5fa0db69635271bc4621cc0b65b2d590 From: Larry Finger Date: Wed, 6 Feb 2013 12:54:17 -0600 Subject: rtlwifi: rtl8192cu: Fix NULL dereference BUG when using new_id When the new_id entry in /sysfs is used for a foreign USB device, rtlwifi BUGS with a NULL pointer dereference because t

Patch Upstream: mac80211: always unblock CSA queue stop when disconnecting

2013-02-20 Thread Gregs git-bot
commit: 5b36ebd8249f403c7edf7cf68d68e9a0d0f55243 From: Johannes Berg Date: Wed, 13 Feb 2013 14:21:45 +0100 Subject: mac80211: always unblock CSA queue stop when disconnecting In some cases when disconnecting after (or during?) CSA the queues might not recover, and then the only way to recover is

Patch Upstream: b43: Increase number of RX DMA slots

2013-02-20 Thread Gregs git-bot
commit: ccae0e50c16a7f7adb029c169147400d1ce9f703 From: Larry Finger Date: Sun, 17 Feb 2013 17:01:20 + Subject: b43: Increase number of RX DMA slots Bastian Bittorf reported that some of the silent freezes on a Linksys WRT54G were due to overflow of the RX DMA ring buffer, which was created wi

Patch Upstream: rtlwifi: usb: allocate URB control message setup_packet and data buffer separately

2013-02-20 Thread Gregs git-bot
commit: bc6b89237acb3dee6af6e64e51a18255fef89cc2 From: Jussi Kivilinna Date: Mon, 18 Feb 2013 10:29:30 +0200 Subject: rtlwifi: usb: allocate URB control message setup_packet and data buffer separately rtlwifi allocates both setup_packet and data buffer of control message urb, using shared kmallo

Re: [PATCH] tools: usb: ffs-test: Fix build failure

2013-02-20 Thread Michal Nazarewicz
On Thu, Feb 21 2013, Maxin B. John wrote: > Hi, > > On Thu, Feb 21, 2013 at 2:06 AM, Greg KH wrote: >> On Thu, Feb 21, 2013 at 01:57:51AM +0200, maxin.j...@gmail.com wrote: >>> From: "Maxin B. John" >>> >>> Fixes this build failure: >>> gcc -Wall -Wextra -g -lpthread -I../include -o testusb testu

Re: [PATCH] tools: usb: ffs-test: Fix build failure

2013-02-20 Thread Michal Nazarewicz
On Thu, Feb 21 2013, maxin.j...@gmail.com wrote: > From: "Maxin B. John" > > Fixes this build failure: > gcc -Wall -Wextra -g -lpthread -I../include -o testusb testusb.c > gcc -Wall -Wextra -g -lpthread -I../include -o ffs-test ffs-test.c > In file included from ffs-test.c:41:0: > ../../include/li

Re: [PATCH] tools: usb: ffs-test: Fix build failure

2013-02-20 Thread Maxin B. John
Hi, On Thu, Feb 21, 2013 at 2:06 AM, Greg KH wrote: > On Thu, Feb 21, 2013 at 01:57:51AM +0200, maxin.j...@gmail.com wrote: >> From: "Maxin B. John" >> >> Fixes this build failure: >> gcc -Wall -Wextra -g -lpthread -I../include -o testusb testusb.c >> gcc -Wall -Wextra -g -lpthread -I../include

Re: [tip:x86/urgent] x86, efi: Make "noefi" really disable EFI runtime serivces

2013-02-20 Thread Yinghai Lu
On Wed, Feb 20, 2013 at 3:25 PM, tip-bot for Matt Fleming wrote: > Commit-ID: fb834c7acc5e140cf4f9e86da93a66de8c0514da > Gitweb: http://git.kernel.org/tip/fb834c7acc5e140cf4f9e86da93a66de8c0514da > Author: Matt Fleming > AuthorDate: Wed, 20 Feb 2013 20:36:12 + > Committer: H. Peter

Re: [PATCH] tools: usb: ffs-test: Fix build failure

2013-02-20 Thread Greg KH
On Thu, Feb 21, 2013 at 01:57:51AM +0200, maxin.j...@gmail.com wrote: > From: "Maxin B. John" > > Fixes this build failure: > gcc -Wall -Wextra -g -lpthread -I../include -o testusb testusb.c > gcc -Wall -Wextra -g -lpthread -I../include -o ffs-test ffs-test.c > In file included from ffs-test.c:41

[PATCH] tools: usb: ffs-test: Fix build failure

2013-02-20 Thread maxin . john
From: "Maxin B. John" Fixes this build failure: gcc -Wall -Wextra -g -lpthread -I../include -o testusb testusb.c gcc -Wall -Wextra -g -lpthread -I../include -o ffs-test ffs-test.c In file included from ffs-test.c:41:0: ../../include/linux/usb/functionfs.h:4:39: fatal error: uapi/linux/usb/functio

Re: [PATCH] x86, efi: Make "noefi" really disable EFI runtime serivces

2013-02-20 Thread H. Peter Anvin
On 02/20/2013 03:46 PM, Satoru Takeuchi wrote: > > Sorry, my patch was imperfect. This patch looks good to me. > Perfection is something very rarely achieved. That's why we work with gradual improvements. -hpa -- To unsubscribe from this list: send the line "unsubscribe stable" in the

Re: [PATCH] x86, efi: Make "noefi" really disable EFI runtime serivces

2013-02-20 Thread Satoru Takeuchi
Hi Matt, (2013/02/21 5:36), Matt Fleming wrote: > From: Matt Fleming > > commit 1de63d60cd5b ("efi: Clear EFI_RUNTIME_SERVICES rather than > EFI_BOOT by "noefi" boot parameter") attempted to make "noefi" true to > its documentation and disable EFI runtime services to prevent the > bricking bug d

Patch Upstream: ab8500-chargalg: Only root should have write permission on sysfs file

2013-02-20 Thread Gregs git-bot
commit: e3455002d04276c256a531f7175dce0f7d1cb78a From: Lee Jones Date: Thu, 17 Jan 2013 14:21:53 + Subject: ab8500-chargalg: Only root should have write permission on sysfs file Only root should have write permission on sysfs file ab8500_chargalg/chargalg. Cc: stable@vger.kernel.org Signed-

Patch Upstream: bq27x00_battery: Fix bugs introduced with BQ27425 support

2013-02-20 Thread Gregs git-bot
commit: bde83b9a6b44c1e0fd872e57ecc869cfcf88538f From: NeilBrown Date: Sun, 2 Dec 2012 20:34:21 +1100 Subject: bq27x00_battery: Fix bugs introduced with BQ27425 support commit a66f59ba2e994bf70274ef0513e24e0e7ae20c63 bq27x00_battery: Add support for BQ27425 chip introduced 2 bugs. 1/ 'chip

Patch Upstream: ACPI: Add DMI entry for Sony VGN-FW41E_H

2013-02-20 Thread Gregs git-bot
commit: 66f2fda93b67fa744d406e6dcf443f67bac204b6 From: Joseph Salisbury Date: Tue, 5 Feb 2013 00:16:29 + Subject: ACPI: Add DMI entry for Sony VGN-FW41E_H This patch adds a quirk to allow the Sony VGN-FW41E_H to suspend/resume properly. References: http://bugs.launchpad.net/bugs/1113547 Sign

Patch Upstream: ab8500_btemp: Demote initcall sequence

2013-02-20 Thread Gregs git-bot
commit: eeb0751c99522a4d1bbcc7b6bc1460cd07d07488 From: "Rajanikanth H.V" Date: Wed, 23 Jan 2013 09:56:45 +0530 Subject: ab8500_btemp: Demote initcall sequence Power supply subsystem creates thermal zone device for the property 'POWER_SUPPLY_PROP_TEMP' which requires thermal subsystem to be ready

Patch Upstream: cpuset: fix cpuset_print_task_mems_allowed() vs rename() race

2013-02-20 Thread Gregs git-bot
commit: 63f43f55c9bbc14f76b582644019b8a07dc8219a From: Li Zefan Date: Fri, 25 Jan 2013 16:08:01 +0800 Subject: cpuset: fix cpuset_print_task_mems_allowed() vs rename() race rename() will change dentry->d_name. The result of this race can be worse than seeing partially rewritten name, but we might

Patch Upstream: arm64: compat: use compat_uptr_t type for compat_ucontext.uc_link

2013-02-20 Thread Gregs git-bot
commit: c0e01d5d8f15c085236df184e5bc3d79a8b700cd From: Will Deacon Date: Wed, 6 Feb 2013 11:42:23 + Subject: arm64: compat: use compat_uptr_t type for compat_ucontext.uc_link struct compat_ucontext * is a 64-bit pointer, so we need to use a compat_uptr_t instead to avoid declaring a structure

Patch Upstream: cgroup: fix exit() vs rmdir() race

2013-02-20 Thread Gregs git-bot
commit: 71b5707e119653039e6e95213f00479668c79b75 From: Li Zefan Date: Thu, 24 Jan 2013 14:43:28 +0800 Subject: cgroup: fix exit() vs rmdir() race In cgroup_exit() put_css_set_taskexit() is called without any lock, which might lead to accessing a freed cgroup: thread1 th

Patch Upstream: ARM: 7643/1: sched: correct update_sched_clock()

2013-02-20 Thread Gregs git-bot
commit: 7c4e9ced424be4d36df6a3e3825763e97ee97607 From: Joonsoo Kim Date: Sat, 9 Feb 2013 05:52:45 +0100 Subject: ARM: 7643/1: sched: correct update_sched_clock() If we want load epoch_cyc and epoch_ns atomically, we should update epoch_cyc_copy first of all. This notify reader that updating is in

Re: Kernel 3.0.X Linux kernel race condition with PTRACE_SETREGS CVE-2013-0871

2013-02-20 Thread Ben Hutchings
On Wed, 2013-02-20 at 17:29 +0100, Oleg Nesterov wrote: > Hi Ben, > > sorry for delay, > > On 02/20, Ben Hutchings wrote: > > > > On Tue, 2013-02-19 at 20:35 +0100, Stefan Priebe wrote: > > > Am 19.02.2013 20:05, schrieb Ben Hutchings: > > > > On Tue, Feb 19, 2013 at 06:51:53AM -0800, Greg KH wro

[tip:x86/urgent] x86, efi: Make "noefi" really disable EFI runtime serivces

2013-02-20 Thread tip-bot for Matt Fleming
Commit-ID: fb834c7acc5e140cf4f9e86da93a66de8c0514da Gitweb: http://git.kernel.org/tip/fb834c7acc5e140cf4f9e86da93a66de8c0514da Author: Matt Fleming AuthorDate: Wed, 20 Feb 2013 20:36:12 + Committer: H. Peter Anvin CommitDate: Wed, 20 Feb 2013 13:18:36 -0800 x86, efi: Make "noefi" r

+ posix-timer-dont-call-idr_find-w-out-of-range-id.patch added to -mm tree

2013-02-20 Thread akpm
The patch titled Subject: posix-timer: don't call idr_find() w/ out-of-range ID has been added to the -mm tree. Its filename is posix-timer-dont-call-idr_find-w-out-of-range-id.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc

Re: [PATCH] nohz: Make tick_nohz_irq_exit() irq safe

2013-02-20 Thread Thomas Gleixner
On Wed, 20 Feb 2013, Frederic Weisbecker wrote: > 2013/2/20 Thomas Gleixner : > > That's not a fix. That's an hack. > > I know it looks that way. That's because it's a pure regression fix, > minimal for backportability. > > I'm distinguishing two different things here: the fact that some archs >

+ posix-timer-dont-call-idr_find-w-out-of-range-id.patch added to -mm tree

2013-02-20 Thread akpm
The patch titled Subject: posix-timer: don't call idr_find() w/ out-of-range ID has been added to the -mm tree. Its filename is posix-timer-dont-call-idr_find-w-out-of-range-id.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc

Re: Kernel 3.0.X Linux kernel race condition with PTRACE_SETREGS CVE-2013-0871

2013-02-20 Thread Oleg Nesterov
On 02/20, Shuah Khan wrote: > > On Wed, Feb 20, 2013 at 1:35 PM, Stefan Priebe wrote: > > at least 3.2 stable got all 5 backports: > > 6d0d3f3aca8f6ec0cd91d062abab0196905a9352 > > 667958738244e5be2cb1e05ab1f2a112c52e1c64 > > bb24eda9eee7a1cc865bb10dbb89edf7c1f5cdc7 > > f224540e9fc7be42e1867f1e4967

Re: [PATCH] nohz: Make tick_nohz_irq_exit() irq safe

2013-02-20 Thread Frederic Weisbecker
2013/2/20 Thomas Gleixner : > On Wed, 20 Feb 2013, Frederic Weisbecker wrote: > >> As it stands, irq_exit() may or may not be called with >> irqs disabled, depending on __ARCH_IRQ_EXIT_IRQS_DISABLED >> that the arch can define. >> >> It makes tick_nohz_irq_exit() unsafe. For example two >> interrup

+ keys-revert-one-application-of-fix-unreachable-code-patch.patch added to -mm tree

2013-02-20 Thread akpm
The patch titled Subject: keys: revert one application of "Fix unreachable code" patch has been added to the -mm tree. Its filename is keys-revert-one-application-of-fix-unreachable-code-patch.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed

Re: Kernel 3.0.X Linux kernel race condition with PTRACE_SETREGS CVE-2013-0871

2013-02-20 Thread Shuah Khan
On Wed, Feb 20, 2013 at 1:35 PM, Stefan Priebe wrote: > at least 3.2 stable got all 5 backports: > 6d0d3f3aca8f6ec0cd91d062abab0196905a9352 > 667958738244e5be2cb1e05ab1f2a112c52e1c64 > bb24eda9eee7a1cc865bb10dbb89edf7c1f5cdc7 > f224540e9fc7be42e1867f1e4967889b29073abb > 8957028bd89221048c784d524ee

+ tmpfs-fix-use-after-free-of-mempolicy-object.patch added to -mm tree

2013-02-20 Thread akpm
The patch titled Subject: tmpfs: fix use-after-free of mempolicy object has been added to the -mm tree. Its filename is tmpfs-fix-use-after-free-of-mempolicy-object.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable m

Re: [PATCH] nohz: Make tick_nohz_irq_exit() irq safe

2013-02-20 Thread Thomas Gleixner
On Wed, 20 Feb 2013, Frederic Weisbecker wrote: > As it stands, irq_exit() may or may not be called with > irqs disabled, depending on __ARCH_IRQ_EXIT_IRQS_DISABLED > that the arch can define. > > It makes tick_nohz_irq_exit() unsafe. For example two > interrupts can race in tick_nohz_stop_sched_

[PATCH] x86, efi: Make "noefi" really disable EFI runtime serivces

2013-02-20 Thread Matt Fleming
From: Matt Fleming commit 1de63d60cd5b ("efi: Clear EFI_RUNTIME_SERVICES rather than EFI_BOOT by "noefi" boot parameter") attempted to make "noefi" true to its documentation and disable EFI runtime services to prevent the bricking bug described in commit e0094244e41c ("samsung-laptop: Disable on

Re: Kernel 3.0.X Linux kernel race condition with PTRACE_SETREGS CVE-2013-0871

2013-02-20 Thread Stefan Priebe
at least 3.2 stable got all 5 backports: 6d0d3f3aca8f6ec0cd91d062abab0196905a9352 667958738244e5be2cb1e05ab1f2a112c52e1c64 bb24eda9eee7a1cc865bb10dbb89edf7c1f5cdc7 f224540e9fc7be42e1867f1e4967889b29073abb 8957028bd89221048c784d524ee42513356fc822 Stefan Am 20.02.2013 17:29, schrieb Oleg Nesterov:

Re: [stable request] fix for nouveau mem corruption [was: WARNING: at drivers/gpu/drm/nouveau/core/core/mm.c:242]

2013-02-20 Thread Marcin Slusarz
On Wed, Feb 20, 2013 at 03:47:05PM +0100, Jiri Slaby wrote: > On 02/19/2013 08:07 AM, Marcin Slusarz wrote: > >>> Crash/warning should be fixed by commit > >>> cfd376b6bfccf33782a0748a9c70f7f752f8b869 > >>> "drm/nouveau/vm: fix memory corruption when pgt allocation fails". > >> > >> Oh, thanks for

Re: [PATCH stable-3.0] x86: Do not leak kernel page mapping locations

2013-02-20 Thread H. Peter Anvin
On 02/20/2013 12:21 AM, CAI Qian wrote: > Hello Ingo, Peter or Kees, > > This is to back-port to stable-3.0 that only adjusted the context that > need your review please. > Looks right to me. -hpa -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a me

[PATCH 3.7.y 3.8.y] perf hists: Fix period symbol_conf.field_sep display

2013-02-20 Thread Josh Boyer
From: Jiri Olsa Upstream commit c0d246b85fc7d42688d7a5d999ea671777caf65b Currently we don't properly display hist data with symbol_conf.field_sep separator. We need to display either space or separator. Signed-off-by: Jiri Olsa Cc: Arnaldo Carvalho de Melo Cc: Peter Zijlstra Cc: Ingo Molnar

[PATCH] drm/i915: Fix up mismerge of 3490ea5d in 3.7.y

2013-02-20 Thread Adam Jackson
The 3.7.y version of this seems to have missed a hunk in i9xx_update_wm. Tested-by: Glen Gray Signed-off-by: Adam Jackson --- drivers/gpu/drm/i915/intel_pm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c ind

Re: Kernel 3.0.X Linux kernel race condition with PTRACE_SETREGS CVE-2013-0871

2013-02-20 Thread Oleg Nesterov
Hi Ben, sorry for delay, On 02/20, Ben Hutchings wrote: > > On Tue, 2013-02-19 at 20:35 +0100, Stefan Priebe wrote: > > Am 19.02.2013 20:05, schrieb Ben Hutchings: > > > On Tue, Feb 19, 2013 at 06:51:53AM -0800, Greg KH wrote: > > >> On Tue, Feb 19, 2013 at 10:18:37AM +0100, Stefan Priebe - Profi

Re: [ 1/1] printk: fix buffer overflow when calling log_prefix function from call_console_drivers

2013-02-20 Thread Satoru Takeuchi
At Wed, 20 Feb 2013 14:43:09 +0100, Alexandre SIMON wrote: > > [Satoru Takeuchi] wrote the following on [20/02/2013 14:02]: > [...] > > > > I reviewed this patch and it seems to be good for me. Since I'm not good at > > printk code, I want to confirm whether what I think is correct or not. > > Is

Re: [PATCH] b43: Increase number of RX DMA slots

2013-02-20 Thread Larry Finger
On 02/20/2013 02:15 AM, Bastian Bittorf wrote: * Larry Finger [20.02.2013 08:32]: On 02/20/2013 12:26 AM, Gábor Stefanik wrote: Is this an issue that vendor drivers are also vulnerable to? If it is a firmware issue, I would certainly think so. I also think so, at least if they are using the

[stable request] fix for nouveau mem corruption [was: WARNING: at drivers/gpu/drm/nouveau/core/core/mm.c:242]

2013-02-20 Thread Jiri Slaby
On 02/19/2013 08:07 AM, Marcin Slusarz wrote: >>> Crash/warning should be fixed by commit >>> cfd376b6bfccf33782a0748a9c70f7f752f8b869 >>> "drm/nouveau/vm: fix memory corruption when pgt allocation fails". >> >> Oh, thanks for the pointer. Could that bug cause real "memory >> corruption"? As we're

Re: [ 1/1] printk: fix buffer overflow when calling log_prefix function from call_console_drivers

2013-02-20 Thread Alexandre SIMON
[Satoru Takeuchi] wrote the following on [20/02/2013 14:02]: [...] > > I reviewed this patch and it seems to be good for me. Since I'm not good at > printk code, I want to confirm whether what I think is correct or not. > Is the following my understanding correct? No problem, it's nice to talk

Re: [ 0/1] 3.0.66-stable review

2013-02-20 Thread Satoru Takeuchi
At Mon, 18 Feb 2013 19:49:17 -0700, Shuah Khan wrote: > > On Mon, Feb 18, 2013 at 11:25 AM, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 3.0.66 release. > > There is 1 patch in this series, which will be posted as a response to > > this one. If anyone has

Re: [ 0/1] 3.4.33-stable review

2013-02-20 Thread Satoru Takeuchi
At Tue, 19 Feb 2013 20:31:02 -0700, Shuah Khan wrote: > > On Tue, Feb 19, 2013 at 7:51 PM, Greg Kroah-Hartman > wrote: > > On Mon, Feb 18, 2013 at 07:50:16PM -0700, Shuah Khan wrote: > >> On Mon, Feb 18, 2013 at 11:24 AM, Greg Kroah-Hartman > >> wrote: > >> > This is the start of the stable revi

Patch Upstream: workqueue: consider work function when searching for busy work items

2013-02-20 Thread Gregs git-bot
commit: a2c1c57be8d9fd5b716113c8991d3d702eeacf77 From: Tejun Heo Date: Tue, 18 Dec 2012 10:35:02 -0800 Subject: workqueue: consider work function when searching for busy work items To avoid executing the same work item concurrenlty, workqueue hashes currently busy workers according to their curre

Patch Upstream: workqueue: un-GPL function delayed_work_timer_fn()

2013-02-20 Thread Gregs git-bot
commit: 1438ade5670b56d5386c220e1ad4b5a824a1e585 From: Konstantin Khlebnikov Date: Thu, 24 Jan 2013 16:36:31 +0400 Subject: workqueue: un-GPL function delayed_work_timer_fn() commit d8e794dfd51c368ed3f686b7f4172830b60ae47b ("workqueue: set delayed_work->timer function on initialization") exports

Re: [ 1/1] printk: fix buffer overflow when calling log_prefix function from call_console_drivers

2013-02-20 Thread Satoru Takeuchi
Hi Alexandre, At Mon, 18 Feb 2013 10:24:56 -0800, Greg Kroah-Hartman wrote: > > 3.4-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Alexandre SIMON > > This patch corrects a buffer overflow in kernels from 3.0 to 3.4 when calling > log_

[PATCH stable-3.0] x86: Do not leak kernel page mapping locations

2013-02-20 Thread CAI Qian
Hello Ingo, Peter or Kees, This is to back-port to stable-3.0 that only adjusted the context that need your review please. Regards, CAI Qian >From e575a86fdc50d013bf3ad3aa81d9100e8e6cc60d Mon Sep 17 00:00:00 2001 From: Kees Cook Date: Thu, 7 Feb 2013 09:44:13 -0800 Subject: [PATCH] x86: Do not

Re: [PATCH] b43: Increase number of RX DMA slots

2013-02-20 Thread Bastian Bittorf
* Larry Finger [20.02.2013 08:32]: > On 02/20/2013 12:26 AM, Gábor Stefanik wrote: > > > >Is this an issue that vendor drivers are also vulnerable to? If it is > >a firmware issue, I would certainly think so. > > I also think so, at least if they are using the firmware version that > Bastian is u