From: Parav Pandit <parav@mellanox.com>
To: Leon Romanovsky <leon@kernel.org>,
Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: RE: [PATCH rdma-next 2/2] RDMA/core: Check that process is still alive before sending it to the users
Date: Mon, 7 Oct 2019 18:58:13 +0000 [thread overview]
Message-ID: <AM0PR05MB4866CB24D8105C83B31988A3D19B0@AM0PR05MB4866.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20191002123245.18153-3-leon@kernel.org>
> -----Original Message-----
> From: linux-rdma-owner@vger.kernel.org <linux-rdma-
> owner@vger.kernel.org> On Behalf Of Leon Romanovsky
> Sent: Wednesday, October 2, 2019 7:33 AM
> To: Doug Ledford <dledford@redhat.com>; Jason Gunthorpe
> <jgg@mellanox.com>
> Cc: Leon Romanovsky <leonro@mellanox.com>; RDMA mailing list <linux-
> rdma@vger.kernel.org>
> Subject: [PATCH rdma-next 2/2] RDMA/core: Check that process is still alive
> before sending it to the users
>
> From: Leon Romanovsky <leonro@mellanox.com>
>
> The PID information can disappear asynchronically because task can be killed
> and moved to zombie state. In such case, PID will be zero in similar way to the
> kernel tasks. Recognize such situation where we are asking to return orphaned
> object and simply skip filling PID attribute.
>
> As part of this change, document the same scenario in counter.c code.
>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> ---
> drivers/infiniband/core/counters.c | 14 ++++++++++++--
> drivers/infiniband/core/nldev.c | 31 ++++++++++++++++++++++--------
> 2 files changed, 35 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/infiniband/core/counters.c
> b/drivers/infiniband/core/counters.c
> index 12ba2685abcf..47c551a0bcb0 100644
> --- a/drivers/infiniband/core/counters.c
> +++ b/drivers/infiniband/core/counters.c
> @@ -149,8 +149,18 @@ static bool auto_mode_match(struct ib_qp *qp, struct
> rdma_counter *counter,
> struct auto_mode_param *param = &counter->mode.param;
> bool match = true;
>
> - /* Ensure that counter belongs to the right PID */
> - if (task_pid_nr(counter->res.task) != task_pid_nr(qp->res.task))
> + /*
> + * Ensure that counter belongs to the right PID.
> + * This operation can race with user space which kills
> + * the process and leaves QP and counters orphans.
> + *
> + * It is not a big deal because exitted task will leave both
> + * QP and counter in the same bucket of zombie process. Just ensure
> + * that process is still alive before procedding.
> + *
> + */
> + if (task_pid_nr(counter->res.task) != task_pid_nr(qp->res.task) ||
> + !task_pid_nr(qp->res.task))
> return false;
>
> if (auto_mask & RDMA_COUNTER_MASK_QP_TYPE) diff --git
> a/drivers/infiniband/core/nldev.c b/drivers/infiniband/core/nldev.c index
> 71bc08510064..c6fe0c52f6dc 100644
> --- a/drivers/infiniband/core/nldev.c
> +++ b/drivers/infiniband/core/nldev.c
> @@ -399,20 +399,35 @@ static int fill_res_info(struct sk_buff *msg, struct
> ib_device *device) static int fill_res_name_pid(struct sk_buff *msg,
> struct rdma_restrack_entry *res) {
> + int err = 0;
> + pid_t pid;
> +
> /*
> * For user resources, user is should read /proc/PID/comm to get the
> * name of the task file.
> */
> if (rdma_is_kernel_res(res)) {
> - if (nla_put_string(msg,
> RDMA_NLDEV_ATTR_RES_KERN_NAME,
> - res->kern_name))
> - return -EMSGSIZE;
> - } else {
> - if (nla_put_u32(msg, RDMA_NLDEV_ATTR_RES_PID,
> - task_pid_vnr(res->task)))
> - return -EMSGSIZE;
> + err = nla_put_string(msg,
> RDMA_NLDEV_ATTR_RES_KERN_NAME,
> + res->kern_name);
> + goto out;
> }
> - return 0;
> +
> + pid = task_pid_vnr(res->task);
> + /*
> + * PID == 0 returns in two scenarios:
> + * 1. It is kernel task, but because we checked above, it won't be
> possible.
Please drop above comment point 1. See more below.
> + * 2. Task is dead and in zombie state. There is no need to print PID
> anymore.
> + */
> + if (pid)
> + /*
> + * This part is racy, task can be killed and PID will be zero right
> + * here but it is ok, next query won't return PID. We don't
> promise
> + * real-time reflection of SW objects.
> + */
> + err = nla_put_u32(msg, RDMA_NLDEV_ATTR_RES_PID, pid);
> +
> +out:
> + return err ? -EMSGSIZE : 0;
> }
Below code reads better along with rest of the comments in the patch.
if (kern_resource) {
err = nla_put_string(msg, RDMA_NLDEV_ATTR_RES_KERN_NAME,
res->kern_name);
} else {
pid_t pid;
pid = task_pid_vnr(res->task);
if (pid)
err = nla_put_u32(msg, RDMA_NLDEV_ATTR_RES_PID, pid);
}
>
> static bool fill_res_entry(struct ib_device *dev, struct sk_buff *msg,
> --
> 2.20.1
next prev parent reply other threads:[~2019-10-07 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 12:32 [PATCH rdma-next 0/2] Remove PID namespaces support from restrack Leon Romanovsky
2019-10-02 12:32 ` [PATCH rdma-next 1/2] RDMA/restrack: Remove PID namespace support Leon Romanovsky
2019-10-02 12:32 ` [PATCH rdma-next 2/2] RDMA/core: Check that process is still alive before sending it to the users Leon Romanovsky
2019-10-07 18:58 ` Parav Pandit [this message]
2019-10-08 7:52 ` Leon Romanovsky
2019-10-08 13:46 ` Parav Pandit
2019-10-08 19:11 ` Jason Gunthorpe
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=AM0PR05MB4866CB24D8105C83B31988A3D19B0@AM0PR05MB4866.eurprd05.prod.outlook.com \
--to=parav@mellanox.com \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@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).