From: Jason Gunthorpe <jgg@mellanox.com>
To: Ajay Kaher <akaher@vmware.com>
Cc: "aarcange@redhat.com" <aarcange@redhat.com>,
"jannh@google.com" <jannh@google.com>,
"oleg@redhat.com" <oleg@redhat.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"rppt@linux.ibm.com" <rppt@linux.ibm.com>,
"mhocko@suse.com" <mhocko@suse.com>,
Yishai Hadas <yishaih@mellanox.com>,
"dledford@redhat.com" <dledford@redhat.com>,
"sean.hefty@intel.com" <sean.hefty@intel.com>,
"hal.rosenstock@gmail.com" <hal.rosenstock@gmail.com>,
Matan Barak <matanb@mellanox.com>,
Leon Romanovsky <leonro@mellanox.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"srivatsab@vmware.com" <srivatsab@vmware.com>,
"amakhalov@vmware.com" <amakhalov@vmware.com>
Subject: Re: [PATCH] [v4.14.y] infiniband: fix race condition between infiniband mlx4, mlx5 driver and core dumping
Date: Mon, 10 Jun 2019 16:05:27 +0000 [thread overview]
Message-ID: <20190610160521.GJ18446@mellanox.com> (raw)
In-Reply-To: <1560199937-23476-1-git-send-email-akaher@vmware.com>
On Tue, Jun 11, 2019 at 02:22:17AM +0530, Ajay Kaher wrote:
> This patch is the extension of following upstream commit to fix
> the race condition between get_task_mm() and core dumping
> for IB->mlx4 and IB->mlx5 drivers:
>
> commit 04f5866e41fb ("coredump: fix race condition between
> mmget_not_zero()/get_task_mm() and core dumping")'
>
> Thanks to Jason for pointing this.
>
> Signed-off-by: Ajay Kaher <akaher@vmware.com>
> ---
> drivers/infiniband/hw/mlx4/main.c | 4 +++-
> drivers/infiniband/hw/mlx5/main.c | 3 +++
> 2 files changed, 6 insertions(+), 1 deletion(-)
Acked-by: Jason Gunthorpe <jgg@mellanox.com>
Jason
next prev parent reply other threads:[~2019-06-10 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 20:52 [PATCH] [v4.14.y] infiniband: fix race condition between infiniband mlx4, mlx5 driver and core dumping Ajay Kaher
2019-06-10 13:55 ` Michal Hocko
2019-06-10 16:05 ` Jason Gunthorpe [this message]
2019-06-14 14:41 ` Ajay Kaher
2019-06-14 14:55 ` Greg KH
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=20190610160521.GJ18446@mellanox.com \
--to=jgg@mellanox.com \
--cc=aarcange@redhat.com \
--cc=akaher@vmware.com \
--cc=amakhalov@vmware.com \
--cc=dledford@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=jannh@google.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=mhocko@suse.com \
--cc=oleg@redhat.com \
--cc=peterx@redhat.com \
--cc=rppt@linux.ibm.com \
--cc=sean.hefty@intel.com \
--cc=srivatsab@vmware.com \
--cc=stable@vger.kernel.org \
--cc=yishaih@mellanox.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;
as well as URLs for NNTP newsgroup(s).