From: Greg KH <greg@kroah.com>
To: Mike Marciniszyn <mike.marciniszyn@intel.com>
Cc: stable@vger.kernel.org, linux-rdma@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: [PATCH v2] IB/hfi1: Protect the global dev_cntr_names and port_cntr_names
Date: Tue, 23 May 2017 21:55:33 +0200 [thread overview]
Message-ID: <20170523195533.GA17694@kroah.com> (raw)
In-Reply-To: <20170523194407.28059.59929.stgit@phlsvslse11.ph.intel.com>
On Tue, May 23, 2017 at 03:44:29PM -0400, Mike Marciniszyn wrote:
> From: Tadeusz Struk <tadeusz.struk@intel.com>
>
> commit 62eed66e98b4c2286fef2ce5911d8d75b7515f7b upstream.
>
> Protect the global dev_cntr_names and port_cntr_names with the global
> mutex as they are allocated and freed in a function called per device.
> Otherwise there is a danger of double free and memory leaks.
>
> Cc: stable <stable@vger.kernel.org> # v4.10
Why resend this???
next prev parent reply other threads:[~2017-05-23 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 19:44 [PATCH v2] IB/hfi1: Protect the global dev_cntr_names and port_cntr_names Mike Marciniszyn
2017-05-23 19:55 ` Greg KH [this message]
2017-05-23 19:59 ` Marciniszyn, Mike
2017-05-23 20:06 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2017-05-23 19:42 Mike Marciniszyn
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=20170523195533.GA17694@kroah.com \
--to=greg@kroah.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=stable-commits@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).