From: Paul Menzel <paul.menzel@giantmonkey.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Ben Hutchings <ben@decadent.org.uk>,
"James E. J. Bottomley" <JBottomley@odin.com>,
SCSI development list <linux-scsi@vger.kernel.org>,
801925@bugs.debian.org, Erich Schubert <erich@debian.org>,
Alexandre Rossi <alexandre.rossi@gmail.com>
Subject: Re: NULL pointer dereference: IP: [<f828a00c>] sr_runtime_suspend+0xc/0x20 [sr_mod]
Date: Sat, 09 Jan 2016 16:23:52 +0100 [thread overview]
Message-ID: <1452353032.1150.4.camel@giantmonkey.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1510312200080.24212-100000@netrider.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
Version: 4.4~rc8-1~exp1
Dear Alan,
Thank you for your help!
There were some follow-ups to the bug report [1], but I think you and I
were not in CC.
Am Samstag, den 31.10.2015, 22:05 -0400 schrieb Alan Stern:
> On Sat, 31 Oct 2015, Alan Stern wrote:
>
> > I believe the problem shown in that photo was fixed by commit
> > 49718f0fb8c9 ("SCSI: Fix NULL pointer dereference in runtime PM"),
> > which was merged in 4.2 and has been back-ported to various stable
> > releases.
>
> On second thought, it seems more likely that this issue probably was
> _caused_ by that commit. The fix can be found in these two emails:
>
> http://marc.info/?l=linux-scsi&m=144185206825609&w=2
> http://marc.info/?l=linux-scsi&m=144185208525611&w=2
>
> which have not been merged yet as far as I know even though they were
> submitted back in September.
I can only say, that I am still unable to boot my system with Linux
4.4-rc8 [2]. Are these patches included there?
Thanks,
Paul
[1] https://bugs.debian.org/801925
[2] https://packages.debian.org/experimental/linux-image-4.4.0-rc8-686-pae-dbg
--
GPG-Schlüssel: 33623E9B
Fingerabdruck = 0EB1 649D 4361 D04F 3C70 6F71 4DD7 BF75 3362 3E9B
Giant Monkey Software Engineering GmbH
Brunnenstr. 7D
10119 Berlin Mitte
Geschäftsführer Adrian Fuhrmann, Lion Vollnhals und Paul Menzel
USt-IdNr.: DE281524720
HRB 139495 B Amtsgericht Charlottenburg
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-09 15:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 1:05 NULL pointer dereference: IP: [<f828a00c>] sr_runtime_suspend+0xc/0x20 [sr_mod] Paul Menzel
2015-10-16 7:54 ` Paul Menzel
2015-10-16 8:52 ` Paul Menzel
2015-10-20 1:39 ` Ben Hutchings
2015-10-31 9:39 ` Paul Menzel
2015-11-01 1:56 ` Alan Stern
2015-11-01 2:05 ` Alan Stern
2016-01-09 15:23 ` Paul Menzel [this message]
2016-01-09 16:36 ` Alan Stern
2016-01-10 11:44 ` Erich Schubert
2016-01-10 15:32 ` Alan Stern
[not found] <CAGKbab941Nh7Sy1NTZC6ySxG_P5g7HpjATQ_GSCvDY8y=qgmHA@mail.gmail.com>
2016-01-19 16:38 ` Alan Stern
2016-01-19 16:52 ` Paul Menzel
2016-01-19 21:08 ` Alan Stern
2016-01-19 23:20 ` Paul Menzel
2016-01-20 22:07 ` Alexandre Rossi
2016-02-09 16:47 ` Paul Menzel
2016-02-09 19:56 ` Alexandre Rossi
2016-02-09 20:51 ` Ben Hutchings
2016-02-18 16:27 ` Alan Stern
2016-02-22 23:15 ` Alexandre Rossi
2016-02-23 15:14 ` Alan Stern
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=1452353032.1150.4.camel@giantmonkey.de \
--to=paul.menzel@giantmonkey.de \
--cc=801925@bugs.debian.org \
--cc=JBottomley@odin.com \
--cc=alexandre.rossi@gmail.com \
--cc=ben@decadent.org.uk \
--cc=erich@debian.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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