From: Sasha Levin <sashal@kernel.org>
To: Ajay Kaher <akaher@vmware.com>
Cc: aarcange@redhat.com, jannh@google.com, oleg@redhat.com,
peterx@redhat.com, rppt@linux.ibm.com, jgg@mellanox.com,
mhocko@suse.com, jglisse@redhat.com, akpm@linux-foundation.org,
mike.kravetz@oracle.com, viro@zeniv.linux.org.uk,
riandrews@android.com, arve@android.com, yishaih@mellanox.com,
dledford@redhat.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com, matanb@mellanox.com,
leonro@mellanox.com, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, devel@driverdev.osuosl.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, srivatsab@vmware.com,
amakhalov@vmware.com
Subject: Re: [PATCH v4 0/3] [v4.9.y] coredump: fix race condition between mmget_not_zero()/get_task_mm() and core dumping
Date: Mon, 24 Jun 2019 16:21:50 -0400 [thread overview]
Message-ID: <20190624202150.GC3881@sasha-vm> (raw)
In-Reply-To: <1561410186-3919-4-git-send-email-akaher@vmware.com>
On Tue, Jun 25, 2019 at 02:33:06AM +0530, Ajay Kaher wrote:
>coredump: fix race condition between mmget_not_zero()/get_task_mm()
>and core dumping
>
>[PATCH v4 1/3]:
>Backporting of commit 04f5866e41fb70690e28397487d8bd8eea7d712a upstream.
>
>[PATCH v4 2/3]:
>Extension of commit 04f5866e41fb to fix the race condition between
>get_task_mm() and core dumping for IB->mlx4 and IB->mlx5 drivers.
>
>[PATCH v4 3/3]
>Backporting of commit 59ea6d06cfa9247b586a695c21f94afa7183af74 upstream.
>
>[diff from v3]:
>- added [PATCH v4 3/3]
Why do all the patches have the same subject line?
I guess it's correct for the first one, but can you explain what's up
with #2 and #3?
If the second one isn't upstream, please explain in detail why not and
how 4.9 differs from upstream so that it requires a custom backport.
The third one just looks like a different patch altogether with a wrong
subject line?
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Ajay Kaher <akaher@vmware.com>
Cc: aarcange@redhat.com, jannh@google.com, oleg@redhat.com,
peterx@redhat.com, rppt@linux.ibm.com, jgg@mellanox.com,
mhocko@suse.com, jglisse@redhat.com, akpm@linux-foundation.org,
mike.kravetz@oracle.com, viro@zeniv.linux.org.uk,
riandrews@android.com, arve@android.com, yishaih@mellanox.com,
dledford@redhat.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com, matanb@mellanox.com,
leonro@mellanox.com, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, devel@driverdev.osuosl.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, srivatsab@vmware.com,
amakhalov@vmware.com
Subject: Re: [PATCH v4 0/3] [v4.9.y] coredump: fix race condition between mmget_not_zero()/get_task_mm() and core dumping
Date: Mon, 24 Jun 2019 16:21:50 -0400 [thread overview]
Message-ID: <20190624202150.GC3881@sasha-vm> (raw)
In-Reply-To: <1561410186-3919-4-git-send-email-akaher@vmware.com>
On Tue, Jun 25, 2019 at 02:33:06AM +0530, Ajay Kaher wrote:
>coredump: fix race condition between mmget_not_zero()/get_task_mm()
>and core dumping
>
>[PATCH v4 1/3]:
>Backporting of commit 04f5866e41fb70690e28397487d8bd8eea7d712a upstream.
>
>[PATCH v4 2/3]:
>Extension of commit 04f5866e41fb to fix the race condition between
>get_task_mm() and core dumping for IB->mlx4 and IB->mlx5 drivers.
>
>[PATCH v4 3/3]
>Backporting of commit 59ea6d06cfa9247b586a695c21f94afa7183af74 upstream.
>
>[diff from v3]:
>- added [PATCH v4 3/3]
Why do all the patches have the same subject line?
I guess it's correct for the first one, but can you explain what's up
with #2 and #3?
If the second one isn't upstream, please explain in detail why not and
how 4.9 differs from upstream so that it requires a custom backport.
The third one just looks like a different patch altogether with a wrong
subject line?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-06-24 20:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 21:03 [PATCH v4 1/3] [v4.9.y] coredump: fix race condition between mmget_not_zero()/get_task_mm() and core dumping Ajay Kaher
2019-06-24 21:03 ` Ajay Kaher
2019-06-24 21:03 ` [PATCH v4 2/3][v4.9.y] " Ajay Kaher
2019-06-24 21:03 ` Ajay Kaher
2019-06-24 13:12 ` Jason Gunthorpe
2019-06-24 13:12 ` Jason Gunthorpe
2019-06-24 21:03 ` [PATCH v4 3/3] [v4.9.y] " Ajay Kaher
2019-06-24 21:03 ` Ajay Kaher
2019-06-24 21:03 ` [PATCH v4 0/3] " Ajay Kaher
2019-06-24 21:03 ` Ajay Kaher
2019-06-24 20:21 ` Sasha Levin [this message]
2019-06-24 20:21 ` Sasha Levin
2019-06-25 6:10 ` Ajay Kaher
2019-06-25 6:10 ` Ajay Kaher
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=20190624202150.GC3881@sasha-vm \
--to=sashal@kernel.org \
--cc=aarcange@redhat.com \
--cc=akaher@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=amakhalov@vmware.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=dledford@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=jannh@google.com \
--cc=jgg@mellanox.com \
--cc=jglisse@redhat.com \
--cc=leonro@mellanox.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=oleg@redhat.com \
--cc=peterx@redhat.com \
--cc=riandrews@android.com \
--cc=rppt@linux.ibm.com \
--cc=sean.hefty@intel.com \
--cc=srivatsab@vmware.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--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 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.