From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
<linux-scsi@vger.kernel.org>,
Michael Hernandez <michael.hernandez@cavium.com>,
Himanshu Madhani <himanshu.madhani@cavium.com>,
Christoph Hellwig <hch@lst.de>, <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] qla2xxx: Fix a recently introduced memory leak
Date: Wed, 25 Jan 2017 18:28:20 -0500 [thread overview]
Message-ID: <yq1tw8mbtyj.fsf@oracle.com> (raw)
In-Reply-To: <20170123163446.9227-2-bart.vanassche@sandisk.com> (Bart Van Assche's message of "Mon, 23 Jan 2017 08:34:45 -0800")
>>>>> "Bart" == Bart Van Assche <bart.vanassche@sandisk.com> writes:
Bart> qla2x00_probe_one() allocates IRQs before it initializes rsp_q_map
Bart> so IRQs must be freed even if rsp_q_map allocation did not occur.
Bart> This was detected by kmemleak.
I queued this one yesterday but was waiting for a resolution on patch
2...
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org,
Michael Hernandez <michael.hernandez@cavium.com>,
Himanshu Madhani <himanshu.madhani@cavium.com>,
Christoph Hellwig <hch@lst.de>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] qla2xxx: Fix a recently introduced memory leak
Date: Wed, 25 Jan 2017 18:28:20 -0500 [thread overview]
Message-ID: <yq1tw8mbtyj.fsf@oracle.com> (raw)
In-Reply-To: <20170123163446.9227-2-bart.vanassche@sandisk.com> (Bart Van Assche's message of "Mon, 23 Jan 2017 08:34:45 -0800")
>>>>> "Bart" == Bart Van Assche <bart.vanassche@sandisk.com> writes:
Bart> qla2x00_probe_one() allocates IRQs before it initializes rsp_q_map
Bart> so IRQs must be freed even if rsp_q_map allocation did not occur.
Bart> This was detected by kmemleak.
I queued this one yesterday but was waiting for a resolution on patch
2...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-01-25 23:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 16:34 [PATCH 0/2] qla2xxx: Two bug fixes Bart Van Assche
2017-01-23 16:34 ` [PATCH 1/2] qla2xxx: Fix a recently introduced memory leak Bart Van Assche
2017-01-23 16:34 ` Bart Van Assche
2017-01-23 16:45 ` Christoph Hellwig
2017-01-23 17:04 ` Madhani, Himanshu
2017-01-24 12:10 ` Johannes Thumshirn
2017-01-24 12:10 ` Johannes Thumshirn
2017-01-25 15:47 ` Bart Van Assche
2017-01-26 14:36 ` hch
2017-01-29 5:17 ` Bart Van Assche
2017-01-29 9:07 ` hch
2017-01-29 17:14 ` Bart Van Assche
2017-01-25 23:28 ` Martin K. Petersen [this message]
2017-01-25 23:28 ` Martin K. Petersen
2017-02-03 16:59 ` Bart Van Assche
2017-02-07 0:23 ` Martin K. Petersen
2017-01-23 16:34 ` [PATCH 2/2] qla2xxx: Avoid that issuing a LIP triggers a kernel crash Bart Van Assche
2017-01-23 16:34 ` Bart Van Assche
2017-01-23 17:41 ` Madhani, Himanshu
2017-01-24 12:12 ` Johannes Thumshirn
2017-01-24 12:12 ` Johannes Thumshirn
2017-01-24 14:59 ` Mauricio Faria de Oliveira
2017-01-25 22:05 ` Madhani, Himanshu
2017-01-25 23:29 ` Martin K. Petersen
2017-01-26 0:09 ` Mauricio Faria de Oliveira
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=yq1tw8mbtyj.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bart.vanassche@sandisk.com \
--cc=hch@lst.de \
--cc=himanshu.madhani@cavium.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michael.hernandez@cavium.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.