public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: lkml@pengaru.com
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: 4.10 rtlwifi regression - NULL pointer dereference
Date: Sun, 8 Jan 2017 20:25:21 -0600	[thread overview]
Message-ID: <20170109022521.GA9125@shells.gnugeneration.com> (raw)
In-Reply-To: <32f982bb-a437-1f40-5306-1069ee8311f9@lwfinger.net>

On Sun, Jan 08, 2017 at 08:03:18PM -0600, Larry Finger wrote:
> On 01/08/2017 07:41 PM, lkml@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.
> > 
> > The network device is a USB dongle:
> > Bus 002 Device 002: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
> > 
> > Reverting 'ba9f93f rtlwifi: Fix enter/exit power_save' prevents the
> > crash.
> > 
> > Sorry I don't have a verbatim capture of the panic, but I was able to
> > catch the relevant parts and rtl_lps_leave() is dereferencing a NULL hw,
> > below setup_arp_tx() and rtl_is_special_data().  That's what led me to
> > reverting ba9f93f since it clearly plays with that stuff.
> > 
> > FWIW machine is a plain X61s thinkpad, 1.8Ghz.
> > 
> 
> You need the patch from
> http://marc.info/?l=linux-wireless&m=148234081512703&w=2. It was pushed with
> the notation that it needed to be included in 4.10; however, it has not yet
> percolated through the system.
> 

Thanks for the quick response Larry, on a Sunday even!

Cheers,
Vito Caputo

      reply	other threads:[~2017-01-09  2:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09  1:41 BUG: 4.10 rtlwifi regression - NULL pointer dereference lkml
2017-01-09  2:03 ` Larry Finger
2017-01-09  2:25   ` lkml [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170109022521.GA9125@shells.gnugeneration.com \
    --to=lkml@pengaru.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox