linux-kernel - Re: [Regression, post-3.5] NULL pointer dereference in usb-wwan after resume from system suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <201208122300.49084.rjw@sisk.pl>
Date:	Sun, 12 Aug 2012 23:00:48 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>
Cc:	linux-usb@...r.kernel.org, Matthias Urlichs <smurf@...rf.noris.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux PM list <linux-pm@...r.kernel.org>
Subject: Re: [Regression, post-3.5] NULL pointer dereference in usb-wwan after resume from system suspend

On Sunday, August 12, 2012, Greg Kroah-Hartman wrote:
> On Sun, Aug 12, 2012 at 12:39:19AM +0200, Rafael J. Wysocki wrote:
> > Hi,
> > 
> > The usb-wwan driver triggers a NULL pointer dereference oops after resume
> > from system suspend on my Toshiba Portege R500, but since that driver
> > hasn't changed since v3.5 and it is only used by the option driver, I suppose
> > that the latter is responsible for that.
> > 
> > This is a clear regression from v3.5, it hasn't happened ever before.
> > 
> > I'll collect some details tomorrow.
> 
> Known bug, we have a fix for it in the usb-next tree now, it will be
> going to Linus in a few days.

Cool. :-)

> If you want, I can dig up the patch for it and send it to you, if it's
> stopping other things from working for you at the moment.

No, it's not delaying me, thanks!

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