From: Sathya Prakash Veerichetty <sathya.prakash@broadcom.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Chaitra Basappa <chaitra.basappa@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
PDL-MPT-FUSIONLINUX <mpt-fusionlinux.pdl@broadcom.com>,
linux-scsi@vger.kernel.org
Subject: RE: [PATCH] mpt3sas: fix possible NULL dereference
Date: Fri, 15 Apr 2016 11:35:48 -0600 [thread overview]
Message-ID: <5b2eca0b5053d01c09f62cf498e3fc0a@mail.gmail.com> (raw)
In-Reply-To: <yq1mvovsiaa.fsf@sermon.lab.mkp.net>
We need to do some more changes in this. The concept is first pool alloc
and then memory alloc in the pool, so the memory has to be freed if the
memory is allocated in the pool and irrespective of memory allocated or
not the pool has to be destroyed if it is created. We will work
internally and provide a complete patch.
Thanks
Sathya
-----Original Message-----
From: Martin K. Petersen [mailto:martin.petersen@oracle.com]
Sent: Thursday, April 14, 2016 8:44 PM
To: Sudip Mukherjee
Cc: Sathya Prakash; Chaitra P B; Suganath Prabu Subramani; James E.J.
Bottomley; Martin K. Petersen; linux-kernel@vger.kernel.org;
MPT-FusionLinux.pdl@broadcom.com; linux-scsi@vger.kernel.org
Subject: Re: [PATCH] mpt3sas: fix possible NULL dereference
>>>>> "Sudip" == Sudip Mukherjee <sudipm.mukherjee@gmail.com> writes:
Sudip> We are dereferencing ioc->sense_dma_pool in pci_pool_free() and
Sudip> after that we are checking if it is NULL, before calling
Sudip> pci_pool_destroy(). Lets check if it is NULL before calling both
Sudip> pci_pool_free() and pci_pool_destroy().
Broadcom folks, please review.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2016-04-15 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 15:42 [PATCH] mpt3sas: fix possible NULL dereference Sudip Mukherjee
2016-04-15 2:43 ` Martin K. Petersen
2016-04-15 17:35 ` Sathya Prakash Veerichetty [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=5b2eca0b5053d01c09f62cf498e3fc0a@mail.gmail.com \
--to=sathya.prakash@broadcom.com \
--cc=chaitra.basappa@broadcom.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpt-fusionlinux.pdl@broadcom.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=suganath-prabu.subramani@broadcom.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