From: Valdis.Kletnieks@vt.edu
To: "Dāvis Mosāns" <davispuh@gmail.com>
Cc: Nicholas Krause <xerofoify@gmail.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Johannes Thumshirn <jthumshirn@suse.de>,
luisbg@osg.samsung.com, Wilfried.Weissmann@gmx.at,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mvsas:Fix possible NULL pointer deference in mvs_dev_found_notify
Date: Wed, 09 Mar 2016 20:18:25 -0500 [thread overview]
Message-ID: <111532.1457572705@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CAOE4rSzh_ipuuWP1=5Kfu1=9-OqH9Nedko3tscJrC4F-GAG0nQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 461 bytes --]
On Wed, 09 Mar 2016 22:33:47 +0200, Dāvis Mosāns said:
> About whether mvs_find_dev_mvi can return NULL it looks like it's possible,
> but I'm not sure if it practically happens. I guess it did hence patch.
Or the "bug" was found by incorrect code inspection. Nick has a history
of submitting patches that are for either non-existent problems or
don't deal with with the issue correctly - bad enough that he's not
allowed to post to the linux-kernel list.
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2016-03-10 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1457531917-568-1-git-send-email-xerofoify@gmail.com>
2016-03-09 20:33 ` Dāvis Mosāns
2016-03-10 1:18 ` Valdis.Kletnieks [this message]
[not found] <1467395018-12365-1-git-send-email-xerofoify@gmail.com>
2016-07-02 11:16 ` Luis de Bethencourt
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=111532.1457572705@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=James.Bottomley@hansenpartnership.com \
--cc=Wilfried.Weissmann@gmx.at \
--cc=davispuh@gmail.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luisbg@osg.samsung.com \
--cc=xerofoify@gmail.com \
/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
all inboxes | Powered by JetHome®