From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hridya Valsaraju <hridya@google.com>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
keescook@google.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
linaro-mm-sig@lists.linaro.org, kaleshsingh@google.com,
surenb@google.com, tjmercier@google.com,
linux-media@vger.kernel.org
Subject: Re: [PATCH] dma-buf: Move sysfs work out of DMA-BUF export/release path
Date: Wed, 5 Jan 2022 16:13:08 +0100 [thread overview]
Message-ID: <YdW1hPRvKYjfORvp@kroah.com> (raw)
In-Reply-To: <20220104235148.21320-1-hridya@google.com>
On Tue, Jan 04, 2022 at 03:51:48PM -0800, Hridya Valsaraju wrote:
> Recently, we noticed an issue where a process went into direct reclaim
> while holding the kernfs rw semaphore for sysfs in write(exclusive)
> mode. This caused processes who were doing DMA-BUF exports and releases
> to go into uninterruptible sleep since they needed to acquire the same
> semaphore for the DMA-BUF sysfs entry creation/deletion. In order to avoid
> blocking DMA-BUF export/release for an indeterminate amount of time
> while another process is holding the sysfs rw semaphore in exclusive
> mode, this patch moves the per-buffer sysfs file creation/deleteion to
> a kthread.
>
> Fixes: bdb8d06dfefd ("dmabuf: Add the capability to expose DMA-BUF stats in sysfs")
> Signed-off-by: Hridya Valsaraju <hridya@google.com>
> ---
> drivers/dma-buf/dma-buf-sysfs-stats.c | 343 ++++++++++++++++++++++++--
> include/linux/dma-buf.h | 46 ++++
> 2 files changed, 366 insertions(+), 23 deletions(-)
Crazy, but if this works in your testing, it looks ok to me. Nice work.
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hridya Valsaraju <hridya@google.com>
Cc: "Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
john.stultz@linaro.org, surenb@google.com,
kaleshsingh@google.com, tjmercier@google.com,
keescook@google.com
Subject: Re: [PATCH] dma-buf: Move sysfs work out of DMA-BUF export/release path
Date: Wed, 5 Jan 2022 16:13:08 +0100 [thread overview]
Message-ID: <YdW1hPRvKYjfORvp@kroah.com> (raw)
In-Reply-To: <20220104235148.21320-1-hridya@google.com>
On Tue, Jan 04, 2022 at 03:51:48PM -0800, Hridya Valsaraju wrote:
> Recently, we noticed an issue where a process went into direct reclaim
> while holding the kernfs rw semaphore for sysfs in write(exclusive)
> mode. This caused processes who were doing DMA-BUF exports and releases
> to go into uninterruptible sleep since they needed to acquire the same
> semaphore for the DMA-BUF sysfs entry creation/deletion. In order to avoid
> blocking DMA-BUF export/release for an indeterminate amount of time
> while another process is holding the sysfs rw semaphore in exclusive
> mode, this patch moves the per-buffer sysfs file creation/deleteion to
> a kthread.
>
> Fixes: bdb8d06dfefd ("dmabuf: Add the capability to expose DMA-BUF stats in sysfs")
> Signed-off-by: Hridya Valsaraju <hridya@google.com>
> ---
> drivers/dma-buf/dma-buf-sysfs-stats.c | 343 ++++++++++++++++++++++++--
> include/linux/dma-buf.h | 46 ++++
> 2 files changed, 366 insertions(+), 23 deletions(-)
Crazy, but if this works in your testing, it looks ok to me. Nice work.
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2022-01-05 15:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 23:51 [PATCH] dma-buf: Move sysfs work out of DMA-BUF export/release path Hridya Valsaraju
2022-01-04 23:51 ` Hridya Valsaraju
2022-01-05 15:13 ` Greg Kroah-Hartman [this message]
2022-01-05 15:13 ` Greg Kroah-Hartman
2022-01-05 18:38 ` Hridya Valsaraju
2022-01-05 18:38 ` Hridya Valsaraju
2022-01-06 8:59 ` Christian König
2022-01-06 8:59 ` Christian König
2022-01-06 19:04 ` Hridya Valsaraju
2022-01-06 19:04 ` Hridya Valsaraju
2022-01-07 10:22 ` Christian König
2022-01-07 10:22 ` Christian König
2022-01-07 18:17 ` Hridya Valsaraju
2022-01-07 18:17 ` Hridya Valsaraju
2022-01-07 21:25 ` Hridya Valsaraju
2022-01-07 21:25 ` Hridya Valsaraju
2022-01-10 7:28 ` Christian König
2022-01-10 7:28 ` Christian König
2022-01-11 6:01 ` Hridya Valsaraju
2022-01-11 6:01 ` Hridya Valsaraju
2022-01-11 8:35 ` Daniel Vetter
2022-01-11 8:35 ` Daniel Vetter
2022-01-11 10:58 ` Christian König
2022-01-11 10:58 ` Christian König
2022-01-11 11:16 ` Greg Kroah-Hartman
2022-01-11 11:16 ` Greg Kroah-Hartman
2022-01-11 11:43 ` Christian König
2022-01-11 11:43 ` Christian König
2022-01-12 1:11 ` Hridya Valsaraju
2022-01-12 1:11 ` Hridya Valsaraju
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=YdW1hPRvKYjfORvp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hridya@google.com \
--cc=kaleshsingh@google.com \
--cc=keescook@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=surenb@google.com \
--cc=tjmercier@google.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.