Re: [PATCH v2] Staging: gasket: Use temporaries to reduce line length.

Wow... I checked, compiled and still sent the wrong thing again. I'm gonna have to give this up soon if i can't get it right. Sandro V > On 10 Sep 2019, at 07:06, Sandro Volery wrote: > > Using temporaries for gasket_page_table entries to remove scnprintf() > statements and reduce line

Re: [PATCH] Fixed most indent issues in tty_io.c

Sandro V > On 7 Sep 2019, at 20:03, Greg KH wrote: > > On Sat, Sep 07, 2019 at 07:49:43PM +0200, Sandro Volery wrote: >> >> >> >> On 7 Sep 2019, at 19:42, Greg KH wrote: >>> >>> On Sat, Sep 07, 2019 at 07:35:42PM +0200, Sandro Volery wrote: On 7 Sep 2019, at

[PATCH] PCI: Do not use bus number zero from EA capability

From: Subbaraya Sundeep As per the spec, "Enhanced Allocation (EA) for Memory and I/O Resources" ECN, approved 23 October 2014, sec 6.9.1.2, fixed bus numbers of a bridge can be zero when no function that uses EA is located behind it. Hence assign bus numbers sequentially when fixed bus numbers

Re: [PATCH 1/5] lib/sort: Make swap functions more generic

Thnk you for the feedback! Andy Shevchenko wrote: > On Thu, Feb 21, 2019 at 06:30:28AM +, George Spelvin wrote: >> +#ifdef CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS > > Why #ifdef is better than if (IS_ENABLED()) ? Because CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS is bool and not tristate.

[v3 PATCH 1/2] PCI: read fixed bus numbers in EA for type 1 functions

From: Subbaraya Sundeep As per the spec - ECN_Enhanced_Allocation_23_Oct_2014_Final and section 6.9.1.2, EA capability contains fixed secondary and subordinate bus numbers for type 1 functions. This patch adds support to read the fixed bus numbers from EA capability for bridge. Signed-off-by:

[v3 PATCH 2/2] PCI: assign bus numbers present in EA capability for bridges

From: Subbaraya Sundeep As per the spec - ECN_Enhanced_Allocation_23_Oct_2014_Final and section 6.9.1.2, bridges with EA capability work with fixed secondary and subordinate bus numbers. Hence consider assigning bus numbers to bridges from EA if the capability exists during the scan.

[PATCH v2] PCI: assign bus numbers present in EA capability for bridges

From: Subbaraya Sundeep As per the spec, bridges with EA capability work with fixed secondary and subordinate bus numbers. Hence assign bus numbers to bridges from EA if the capability exists. Signed-off-by: Subbaraya Sundeep --- Changes for v2: No changes just added Sean Stalley who

[PATCH v2] PCI: assign bus numbers present in EA capability for bridges

From: Subbaraya Sundeep As per the spec, bridges with EA capability work with fixed secondary and subordinate bus numbers. Hence assign bus numbers to bridges from EA if the capability exists. Signed-off-by: Subbaraya Sundeep --- Changes for v2: No changes just added Sean Stalley who

[PATCH] PCI: assign bus numbers present in EA capability for bridges

From: Subbaraya Sundeep As per the spec, bridges with EA capability work with fixed secondary and subordinate bus numbers. Hence assign bus numbers to bridges from EA if the capability exists. Signed-off-by: Subbaraya Sundeep --- drivers/pci/probe.c | 58

[PATCH] PCI: assign bus numbers present in EA capability for bridges

From: Subbaraya Sundeep As per the spec, bridges with EA capability work with fixed secondary and subordinate bus numbers. Hence assign bus numbers to bridges from EA if the capability exists. Signed-off-by: Subbaraya Sundeep --- drivers/pci/probe.c | 58

Re: [PATCH v2] lib/extable.c: use bsearch() library function in search_extable()

With kind regards Thomas > Am 04.06.2017 um 00:38 schrieb Thomas Meyer : > > Signed-off-by: Thomas Meyer > --- > include/linux/extable.h | 3 ++- > kernel/extable.c| 2 +- > kernel/module.c | 2 +- > lib/extable.c | 38

Re: [PATCH v2] lib/extable.c: use bsearch() library function in search_extable()

With kind regards Thomas > Am 04.06.2017 um 00:38 schrieb Thomas Meyer : > > Signed-off-by: Thomas Meyer > --- > include/linux/extable.h | 3 ++- > kernel/extable.c| 2 +- > kernel/module.c | 2 +- > lib/extable.c | 38 +++--- > 4

Re: [BUG nohz]: wrong user and system time accounting

one jiffie. This would imply that > > vtime_account_user() > > is being called less than one jiffie since the last accounting, but I > > haven't > > confirmed any of this yet. > > Jiffies should be advanced by the timer interrupt, on the > housekeeping CPU, which

Re: [BUG nohz]: wrong user and system time accounting

one jiffie. This would imply that > > vtime_account_user() > > is being called less than one jiffie since the last accounting, but I > > haven't > > confirmed any of this yet. > > Jiffies should be advanced by the timer interrupt, on the > housekeeping CPU, which

Re: [BUG] 4.11.0-rc3 xterm hung in D state on exit, wchan is tty_release_struct

On Thu, Mar 23, 2017 at 11:57:22AM -0500, Rob Herring wrote: > On Thu, Mar 23, 2017 at 08:46:03AM -0500, Rob Herring wrote: > > On Thu, Mar 23, 2017 at 12:30:18AM -0700, l...@pengaru.com wrote: > > > On Wed, Mar 22, 2017 at 11:44:18PM -0700, l...@pengaru.com wrote: > > > > On Wed, Mar 22, 2017 at

Re: [BUG] 4.11.0-rc3 xterm hung in D state on exit, wchan is tty_release_struct

On Thu, Mar 23, 2017 at 11:57:22AM -0500, Rob Herring wrote: > On Thu, Mar 23, 2017 at 08:46:03AM -0500, Rob Herring wrote: > > On Thu, Mar 23, 2017 at 12:30:18AM -0700, l...@pengaru.com wrote: > > > On Wed, Mar 22, 2017 at 11:44:18PM -0700, l...@pengaru.com wrote: > > > > On Wed, Mar 22, 2017 at

Re: [BUG] 4.11.0-rc3 xterm hung in D state on exit, wchan is tty_release_struct

On Wed, Mar 22, 2017 at 07:08:46PM -0700, l...@pengaru.com wrote: > Hello list, > > After approximately one day day of running 4.11.0-rc3 with 7e54d9d reverted to > enable regular use, this happened upon destroying an xterm: > > [80817.525112] BUG: unable to handle kernel paging request at

Re: [BUG] 4.11.0-rc3 xterm hung in D state on exit, wchan is tty_release_struct

On Wed, Mar 22, 2017 at 07:08:46PM -0700, l...@pengaru.com wrote: > Hello list, > > After approximately one day day of running 4.11.0-rc3 with 7e54d9d reverted to > enable regular use, this happened upon destroying an xterm: > > [80817.525112] BUG: unable to handle kernel paging request at

Re: [BUG] 4.11.0-rc3 xterm hung in D state on exit, wchan is tty_release_struct

On Wed, Mar 22, 2017 at 11:44:18PM -0700, l...@pengaru.com wrote: > On Wed, Mar 22, 2017 at 07:08:46PM -0700, l...@pengaru.com wrote: > > Hello list, > > > > After approximately one day day of running 4.11.0-rc3 with 7e54d9d reverted > > to > > enable regular use, this happened upon destroying

Re: [BUG] 4.11.0-rc3 xterm hung in D state on exit, wchan is tty_release_struct

On Wed, Mar 22, 2017 at 11:44:18PM -0700, l...@pengaru.com wrote: > On Wed, Mar 22, 2017 at 07:08:46PM -0700, l...@pengaru.com wrote: > > Hello list, > > > > After approximately one day day of running 4.11.0-rc3 with 7e54d9d reverted > > to > > enable regular use, this happened upon destroying

[BUG] 4.11.0-rc3 xterm hung in D state on exit, wchan is tty_release_struct

Hello list, After approximately one day day of running 4.11.0-rc3 with 7e54d9d reverted to enable regular use, this happened upon destroying an xterm: [80817.525112] BUG: unable to handle kernel paging request at 2260 [80817.525239] IP: n_tty_receive_buf_common+0x68/0xab0

[BUG] 4.11.0-rc3 xterm hung in D state on exit, wchan is tty_release_struct

Hello list, After approximately one day day of running 4.11.0-rc3 with 7e54d9d reverted to enable regular use, this happened upon destroying an xterm: [80817.525112] BUG: unable to handle kernel paging request at 2260 [80817.525239] IP: n_tty_receive_buf_common+0x68/0xab0

Re: [Intel-wired-lan] [BUG] 4.11.0-rc1 panic on shutdown X61s

On Tue, Mar 21, 2017 at 07:04:45PM -0700, l...@pengaru.com wrote: > On Thu, Mar 16, 2017 at 08:13:40PM +, Bowers, AndrewX wrote: > > Tested this on a Thinkpad T420i, after verifying it also has an e1000e NIC, > > unable to reproduce. Might be limited to that particular model/firmware > >

Re: [Intel-wired-lan] [BUG] 4.11.0-rc1 panic on shutdown X61s

On Tue, Mar 21, 2017 at 07:04:45PM -0700, l...@pengaru.com wrote: > On Thu, Mar 16, 2017 at 08:13:40PM +, Bowers, AndrewX wrote: > > Tested this on a Thinkpad T420i, after verifying it also has an e1000e NIC, > > unable to reproduce. Might be limited to that particular model/firmware > >

Re: [Intel-wired-lan] [BUG] 4.11.0-rc1 panic on shutdown X61s

On Thu, Mar 16, 2017 at 08:13:40PM +, Bowers, AndrewX wrote: > Tested this on a Thinkpad T420i, after verifying it also has an e1000e NIC, > unable to reproduce. Might be limited to that particular model/firmware > version you're using, which I was not able to track down here although there

Re: [Intel-wired-lan] [BUG] 4.11.0-rc1 panic on shutdown X61s

On Thu, Mar 16, 2017 at 08:13:40PM +, Bowers, AndrewX wrote: > Tested this on a Thinkpad T420i, after verifying it also has an e1000e NIC, > unable to reproduce. Might be limited to that particular model/firmware > version you're using, which I was not able to track down here although there

Re: Still OOM problems with 4.9er/4.10er kernels

On Thu, Mar 16, 2017 at 10:08:44AM +0100, Michal Hocko wrote: > On Thu 16-03-17 01:47:33, l...@pengaru.com wrote: > [...] > > While on the topic of understanding allocation stalls, Philip Freeman > > recently > > mailed linux-kernel with a similar report, and in his case there are plenty > > of

Re: Still OOM problems with 4.9er/4.10er kernels

On Thu, Mar 16, 2017 at 10:08:44AM +0100, Michal Hocko wrote: > On Thu 16-03-17 01:47:33, l...@pengaru.com wrote: > [...] > > While on the topic of understanding allocation stalls, Philip Freeman > > recently > > mailed linux-kernel with a similar report, and in his case there are plenty > > of

Re: Still OOM problems with 4.9er/4.10er kernels

On Thu, Mar 16, 2017 at 09:27:14AM +0100, Michal Hocko wrote: > On Thu 16-03-17 07:38:08, Gerhard Wiesinger wrote: > [...] > > The following commit is included in that version: > > commit 710531320af876192d76b2c1f68190a1df941b02 > > Author: Michal Hocko > > Date: Wed Feb 22

Re: Still OOM problems with 4.9er/4.10er kernels

On Thu, Mar 16, 2017 at 09:27:14AM +0100, Michal Hocko wrote: > On Thu 16-03-17 07:38:08, Gerhard Wiesinger wrote: > [...] > > The following commit is included in that version: > > commit 710531320af876192d76b2c1f68190a1df941b02 > > Author: Michal Hocko > > Date: Wed Feb 22 15:45:58 2017 -0800

Re: [BUG] 4.11.0-rc1 panic on shutdown X61s

On Tue, Mar 14, 2017 at 01:20:27AM +, Brown, Aaron F wrote: > > Borislav Petkov writes: > > > On Sun, Mar 12, 2017 at 03:55:08PM +0200, Andy Shevchenko wrote: > > > > > >> The only change that IMHO matters happened between v4.10 and v4.11- > > rc1 is this: > > >> > > >> @@

Re: [BUG] 4.11.0-rc1 panic on shutdown X61s

On Tue, Mar 14, 2017 at 01:20:27AM +, Brown, Aaron F wrote: > > Borislav Petkov writes: > > > On Sun, Mar 12, 2017 at 03:55:08PM +0200, Andy Shevchenko wrote: > > > > > >> The only change that IMHO matters happened between v4.10 and v4.11- > > rc1 is this: > > >> > > >> @@ -6276,8 +6274,8 @@

Re: [BUG] 4.11.0-rc1 panic on shutdown X61s

On Sun, Mar 12, 2017 at 01:26:21PM +0100, Borislav Petkov wrote: > On Sun, Mar 12, 2017 at 12:57:03PM +0100, Borislav Petkov wrote: > > On Sat, Mar 11, 2017 at 09:37:23PM -0800, l...@pengaru.com wrote: > > > Hello list, > > > > > > Here's a photo of the panic, on imgur to be kind to vger: > > >

Re: [BUG] 4.11.0-rc1 panic on shutdown X61s

On Sun, Mar 12, 2017 at 01:26:21PM +0100, Borislav Petkov wrote: > On Sun, Mar 12, 2017 at 12:57:03PM +0100, Borislav Petkov wrote: > > On Sat, Mar 11, 2017 at 09:37:23PM -0800, l...@pengaru.com wrote: > > > Hello list, > > > > > > Here's a photo of the panic, on imgur to be kind to vger: > > >

[BUG] 4.11.0-rc1 panic on shutdown X61s

Hello list, Here's a photo of the panic, on imgur to be kind to vger: http://imgur.com/a/wZI32 I'm out on a sailboat so can't really do much, but had a chance with internet to send this FYI. I don't even know if this happens always or not yet. Never seen this before, up to and including

[BUG] 4.11.0-rc1 panic on shutdown X61s

Hello list, Here's a photo of the panic, on imgur to be kind to vger: http://imgur.com/a/wZI32 I'm out on a sailboat so can't really do much, but had a chance with internet to send this FYI. I don't even know if this happens always or not yet. Never seen this before, up to and including

Re: [BUG] 4.10-rc8 - ping spinning?

On Thu, Feb 16, 2017 at 10:52:19AM -0500, Soheil Hassas Yeganeh wrote: > On Thu, Feb 16, 2017 at 10:50 AM, Soheil Hassas Yeganeh > wrote: > > Thank you Vito for the report. > > > > The patch you cited actually resolves a similar backward compatibility > > problem for

Re: [BUG] 4.10-rc8 - ping spinning?

On Thu, Feb 16, 2017 at 10:52:19AM -0500, Soheil Hassas Yeganeh wrote: > On Thu, Feb 16, 2017 at 10:50 AM, Soheil Hassas Yeganeh > wrote: > > Thank you Vito for the report. > > > > The patch you cited actually resolves a similar backward compatibility > > problem for traceroute. > > > > I suspect

Re: [BUG] 4.10-rc8 - ping spinning?

Hello netdev, Please see the forwarded message below. This was sent to linux-kernel but after digging a little I suspect it's specific to the network stack. Perusing the net/ changes between 4.9 and 4.10-rc8 this sounded awful related to what I'm observing: commit

Re: [BUG] 4.10-rc8 - ping spinning?

Hello netdev, Please see the forwarded message below. This was sent to linux-kernel but after digging a little I suspect it's specific to the network stack. Perusing the net/ changes between 4.9 and 4.10-rc8 this sounded awful related to what I'm observing: commit

Re: [BUG] 4.10-rc8 - ping spinning?

On Thu, Feb 16, 2017 at 03:03:03AM -0800, l...@pengaru.com wrote: > Hello list, > > Some rtl8192cu bugs of old got me in the habit of running ping in a shelved > (i.e. forgotten) xterm, a harmless practice which seemed to prevent the > rtl8192cu device from dying. > > This evening

Re: [BUG] 4.10-rc8 - ping spinning?

On Thu, Feb 16, 2017 at 03:03:03AM -0800, l...@pengaru.com wrote: > Hello list, > > Some rtl8192cu bugs of old got me in the habit of running ping in a shelved > (i.e. forgotten) xterm, a harmless practice which seemed to prevent the > rtl8192cu device from dying. > > This evening

[BUG] 4.10-rc8 - ping spinning?

Hello list, Some rtl8192cu bugs of old got me in the habit of running ping in a shelved (i.e. forgotten) xterm, a harmless practice which seemed to prevent the rtl8192cu device from dying. This evening the system started getting very slow and to my surprise I found this in `top`:

[BUG] 4.10-rc8 - ping spinning?

Hello list, Some rtl8192cu bugs of old got me in the habit of running ping in a shelved (i.e. forgotten) xterm, a harmless practice which seemed to prevent the rtl8192cu device from dying. This evening the system started getting very slow and to my surprise I found this in `top`:

Re: 4.10-rc1: thinkpad x60: who ate my cpu?

On Mon, Feb 13, 2017 at 12:25:28PM +0100, Thomas Gleixner wrote: > On Mon, 13 Feb 2017, l...@pengaru.com wrote: > > > On Mon, Feb 13, 2017 at 10:42:36AM +0100, Pavel Machek wrote: > > > Hi! > > > > > > On Mon 2017-02-13 09:48:41, Thomas Gleixner wrote: > > > > On Mon, 13 Feb 2017, Pavel Machek

Re: 4.10-rc1: thinkpad x60: who ate my cpu?

On Mon, Feb 13, 2017 at 12:25:28PM +0100, Thomas Gleixner wrote: > On Mon, 13 Feb 2017, l...@pengaru.com wrote: > > > On Mon, Feb 13, 2017 at 10:42:36AM +0100, Pavel Machek wrote: > > > Hi! > > > > > > On Mon 2017-02-13 09:48:41, Thomas Gleixner wrote: > > > > On Mon, 13 Feb 2017, Pavel Machek

Re: 4.10-rc1: thinkpad x60: who ate my cpu?

On Mon, Feb 13, 2017 at 12:25:28PM +0100, Thomas Gleixner wrote: > On Mon, 13 Feb 2017, l...@pengaru.com wrote: > > > On Mon, Feb 13, 2017 at 10:42:36AM +0100, Pavel Machek wrote: > > > Hi! > > > > > > On Mon 2017-02-13 09:48:41, Thomas Gleixner wrote: > > > > On Mon, 13 Feb 2017, Pavel Machek

Re: 4.10-rc1: thinkpad x60: who ate my cpu?

On Mon, Feb 13, 2017 at 12:25:28PM +0100, Thomas Gleixner wrote: > On Mon, 13 Feb 2017, l...@pengaru.com wrote: > > > On Mon, Feb 13, 2017 at 10:42:36AM +0100, Pavel Machek wrote: > > > Hi! > > > > > > On Mon 2017-02-13 09:48:41, Thomas Gleixner wrote: > > > > On Mon, 13 Feb 2017, Pavel Machek

Re: 4.10-rc1: thinkpad x60: who ate my cpu?

On Mon, Feb 13, 2017 at 10:42:36AM +0100, Pavel Machek wrote: > Hi! > > On Mon 2017-02-13 09:48:41, Thomas Gleixner wrote: > > On Mon, 13 Feb 2017, Pavel Machek wrote: > > > cd /sys/devices/system/cpu/cpu1 > > > while true; do echo 0 > online; echo 1 > online; done > > > > > > ...crashes x60

Re: 4.10-rc1: thinkpad x60: who ate my cpu?

On Mon, Feb 13, 2017 at 10:42:36AM +0100, Pavel Machek wrote: > Hi! > > On Mon 2017-02-13 09:48:41, Thomas Gleixner wrote: > > On Mon, 13 Feb 2017, Pavel Machek wrote: > > > cd /sys/devices/system/cpu/cpu1 > > > while true; do echo 0 > online; echo 1 > online; done > > > > > > ...crashes x60

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Mon, Feb 06, 2017 at 07:18:16AM -0800, James Bottomley wrote: > On Mon, 2017-02-06 at 09:50 -0500, Theodore Ts'o wrote: > > On Sun, Feb 05, 2017 at 10:46:23PM -0800, James Bottomley wrote: > > > Yes, I know the problem. However, I believe most current linux > > > filesystems no longer

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Mon, Feb 06, 2017 at 07:18:16AM -0800, James Bottomley wrote: > On Mon, 2017-02-06 at 09:50 -0500, Theodore Ts'o wrote: > > On Sun, Feb 05, 2017 at 10:46:23PM -0800, James Bottomley wrote: > > > Yes, I know the problem. However, I believe most current linux > > > filesystems no longer

Re: BUG: 4.10 i915 drm display noise regression - bisected to a6a7cc4b7

On Mon, Jan 09, 2017 at 12:32:40AM -0600, l...@pengaru.com wrote: > Hello all, > > I'm experiencing display noise in the form of 8x1 pixel bars spuriously > appearing in random locations. This doesn't happen on 4.9, the machine > is an X61s, a Core2Duo 1.8Ghz w/XGA via LVDS. > > I was able to

Re: BUG: 4.10 i915 drm display noise regression - bisected to a6a7cc4b7

On Mon, Jan 09, 2017 at 12:32:40AM -0600, l...@pengaru.com wrote: > Hello all, > > I'm experiencing display noise in the form of 8x1 pixel bars spuriously > appearing in random locations. This doesn't happen on 4.9, the machine > is an X61s, a Core2Duo 1.8Ghz w/XGA via LVDS. > > I was able to

Re: [PATCH v2] drm/i915: Flush untouched framebuffers before display on !llc

On Thu, Jan 12, 2017 at 09:17:06PM +, Chris Wilson wrote: > On Mon, Jan 09, 2017 at 11:19:32AM +, Chris Wilson wrote: > > On a non-llc system, the objects are created with .cache_level = > > CACHE_NONE and so the transition to uncached for scanout is a no-op. > > However, if the object was

Re: [PATCH v2] drm/i915: Flush untouched framebuffers before display on !llc

On Thu, Jan 12, 2017 at 09:17:06PM +, Chris Wilson wrote: > On Mon, Jan 09, 2017 at 11:19:32AM +, Chris Wilson wrote: > > On a non-llc system, the objects are created with .cache_level = > > CACHE_NONE and so the transition to uncached for scanout is a no-op. > > However, if the object was

Re: [PATCH 4.9 003/116] rtlwifi: Fix enter/exit power_save

On Tue, Jan 10, 2017 at 09:40:24PM +0100, Greg Kroah-Hartman wrote: > On Tue, Jan 10, 2017 at 08:40:28PM +0300, Dmitry Osipenko wrote: > > Hello, this patch causes a kernel panic with the rtl8192cu driver. > > Ick, not good! Does this cause a problem in Linus's tree as well? >

Re: [PATCH 4.9 003/116] rtlwifi: Fix enter/exit power_save

On Tue, Jan 10, 2017 at 09:40:24PM +0100, Greg Kroah-Hartman wrote: > On Tue, Jan 10, 2017 at 08:40:28PM +0300, Dmitry Osipenko wrote: > > Hello, this patch causes a kernel panic with the rtl8192cu driver. > > Ick, not good! Does this cause a problem in Linus's tree as well? >

BUG: 4.10 i915 drm display noise regression - bisected to a6a7cc4b7

Hello all, I'm experiencing display noise in the form of 8x1 pixel bars spuriously appearing in random locations. This doesn't happen on 4.9, the machine is an X61s, a Core2Duo 1.8Ghz w/XGA via LVDS. I was able to bisect the issue to a6a7cc4b7: commit a6a7cc4b7db6deaeca11cdd38844ea147a354c7a

BUG: 4.10 i915 drm display noise regression - bisected to a6a7cc4b7

Hello all, I'm experiencing display noise in the form of 8x1 pixel bars spuriously appearing in random locations. This doesn't happen on 4.9, the machine is an X61s, a Core2Duo 1.8Ghz w/XGA via LVDS. I was able to bisect the issue to a6a7cc4b7: commit a6a7cc4b7db6deaeca11cdd38844ea147a354c7a

Re: BUG: 4.10 rtlwifi regression - NULL pointer dereference

On Sun, Jan 08, 2017 at 08:03:18PM -0600, Larry Finger wrote: > On 01/08/2017 07:41 PM, l...@pengaru.com wrote: > > Hello list, > > > > Gave 4.10-rc2 a shot today using the attached config. The kernel panics > > with a NULL pointer dereference upon starting dhclient after > > wpa_supplicant. > >

Re: BUG: 4.10 rtlwifi regression - NULL pointer dereference

On Sun, Jan 08, 2017 at 08:03:18PM -0600, Larry Finger wrote: > On 01/08/2017 07:41 PM, l...@pengaru.com wrote: > > Hello list, > > > > Gave 4.10-rc2 a shot today using the attached config. The kernel panics > > with a NULL pointer dereference upon starting dhclient after > > wpa_supplicant. > >

BUG: 4.10 rtlwifi regression - NULL pointer dereference

Hello list, Gave 4.10-rc2 a shot today using the attached config. The kernel panics with a NULL pointer dereference upon starting dhclient after wpa_supplicant. The network device is a USB dongle: Bus 002 Device 002: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter

BUG: 4.10 rtlwifi regression - NULL pointer dereference

Hello list, Gave 4.10-rc2 a shot today using the attached config. The kernel panics with a NULL pointer dereference upon starting dhclient after wpa_supplicant. The network device is a USB dongle: Bus 002 Device 002: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter

Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog

ad the FAQ at http://www.tux.org/lkml/

Re: [PATCH 4.1 000/159] 4.1.9-stable review

. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog

html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH 4.1 000/159] 4.1.9-stable review

. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH] sysfs.txt: mention that store method buffers are null-terminated

ernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH] debugfs: document that debugfs_remove*() accepts NULL and error values

cribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH] debugfs: document that debugfs_remove*() accepts NULL and error values

all to another debugfs function -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH] sysfs.txt: mention that store method buffers are null-terminated

om this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH] debugfs: document that debugfs_remove*() accepts NULL and error values

cribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH] debugfs: document that debugfs_remove*() accepts NULL and error values

all to another debugfs function -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH] kobject: explain what kobject's sd field is

majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH] Makefile: .PHONY is not a variable, but PHONY is

this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH 1/3] sysfs.txt: fix pre-kernfs sysfs_dirent reference

list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH 3/3] configfs: fix pre-kernfs sysfs_dirent reference

ne "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH 0/3] Fix some outdated pre-kernfs doc references

l.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH 2/3] sysfs-tagging.txt: fix pre-kernfs references

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH] kobject: explain what kobject's sd field is

the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH 1/3] sysfs.txt: fix pre-kernfs sysfs_dirent reference

dule_callback() 函数直接修改。 -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH 0/3] Fix some outdated pre-kernfs doc references

essage to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH 2/3] sysfs-tagging.txt: fix pre-kernfs references

define a type in the kobj_ns_type enumeration. -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH 3/3] configfs: fix pre-kernfs sysfs_dirent reference

2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH] Makefile: .PHONY is not a variable, but PHONY is

ONY: $(PHONY) -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH 4.1 099/123] perf hists browser: Take the --comm, --dsos, etc filters into account

inux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH 4.1 099/123] perf hists browser: Take the --comm, --dsos, etc filters into account

linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: snd_hda_intel headphone output disabling upon complete insertion of plug

n the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: snd_hda_intel headphone output disabling upon complete insertion of plug

is workable for now. Regards, Vito Caputo -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

snd_hda_intel headphone output disabling upon complete insertion of plug

to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

snd_hda_intel headphone output disabling upon complete insertion of plug

...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Commence Industrial Crm Profiled By simply Manufacturing Correspondent Thomas R. Cutler

quot; in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Selling Creative With Nike

ted at http://www.serverphorums.com http://www.serverphorums.com/read.php?12,743667,743667#msg-743667 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Nike Jordan compensated all fines

send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Selling Creative With Nike

://www.serverphorums.com/read.php?12,743667,743667#msg-743667 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Nike Jordan compensated all fines

of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Commence Industrial Crm Profiled By simply Manufacturing Correspondent Thomas R. Cutler

...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Replica Soccer paidat jalkapallon ystäville

kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Replica Soccer paidat jalkapallon ystäville

/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

  1   2   >