From: Charan Teja Kalla <quic_charante@quicinc.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <christian.koenig@amd.com>, <sumit.semwal@linaro.org>,
<hridya@google.com>, <daniel.vetter@ffwll.ch>,
<tjmercier@google.com>, <linux-media@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<linaro-mm-sig@lists.linaro.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] dma-buf: ensure unique directory name for dmabuf stats
Date: Fri, 13 May 2022 15:48:23 +0530 [thread overview]
Message-ID: <2a45f1e1-39d5-76b3-8fd3-c1f8b288afac@quicinc.com> (raw)
In-Reply-To: <Yn4u0AG8iC33S3jO@kroah.com>
On 5/13/2022 3:41 PM, Greg KH wrote:
>> Reported-by: kernel test robot <lkp@intel.com>
> The trest robot did not say that the dmabuf stat name was being
> duplicated, did it?
>
It reported a printk warning on V2[1]. Should we remove this on V3?
@Christian: Could you please drop this tag while merging?
[1] https://lore.kernel.org/all/202205110511.E0d8TXXC-lkp@intel.com/
>> diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
>> index a6fc96e..0ad5039 100644
>> --- a/drivers/dma-buf/dma-buf.c
>> +++ b/drivers/dma-buf/dma-buf.c
>> @@ -407,6 +407,7 @@ static inline int is_dma_buf_file(struct file *file)
>>
>> static struct file *dma_buf_getfile(struct dma_buf *dmabuf, int flags)
>> {
>> + static atomic64_t dmabuf_inode = ATOMIC64_INIT(0);
>> struct file *file;
>> struct inode *inode = alloc_anon_inode(dma_buf_mnt->mnt_sb);
>>
>> @@ -416,6 +417,13 @@ static struct file *dma_buf_getfile(struct dma_buf *dmabuf, int flags)
>> inode->i_size = dmabuf->size;
>> inode_set_bytes(inode, dmabuf->size);
>>
>> + /*
>> + * The ->i_ino acquired from get_next_ino() is not unique thus
>> + * not suitable for using it as dentry name by dmabuf stats.
>> + * Override ->i_ino with the unique and dmabuffs specific
>> + * value.
>> + */
>> + inode->i_ino = atomic64_add_return(1, &dmabuf_inode);
>> file = alloc_file_pseudo(inode, dma_buf_mnt, "dmabuf",
>> flags, &dma_buf_fops);
>> if (IS_ERR(file))
>> --
>> 2.7.4
>>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Thanks for the ACK.
--Charan
next prev parent reply other threads:[~2022-05-13 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 9:38 Charan Teja Kalla
2022-05-13 10:11 ` Greg KH
2022-05-13 10:18 ` Charan Teja Kalla [this message]
2022-05-13 10:26 ` Greg KH
2022-05-13 10:29 ` Christian König
2022-05-13 10:38 ` Charan Teja Kalla
2022-05-13 10:42 ` Christian König
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=2a45f1e1-39d5-76b3-8fd3-c1f8b288afac@quicinc.com \
--to=quic_charante@quicinc.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hridya@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®