From: Danilo Krummrich <dakr@redhat.com>
To: Abhinav Singh <singhabhinav9051571833@gmail.com>,
kherbst@redhat.com, lyude@redhat.com, airlied@gmail.com,
daniel@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v2] driver: gpu: Fixing warning directly dereferencing a rcu pointer
Date: Mon, 13 Nov 2023 20:00:33 +0100 [thread overview]
Message-ID: <8e9efe54-2799-4539-a8b0-aa199f8052f6@redhat.com> (raw)
In-Reply-To: <d0b1fb36-d2a6-446c-8a04-2101981f3a00@gmail.com>
On 11/13/23 19:55, Abhinav Singh wrote:
> On 11/14/23 00:19, Danilo Krummrich wrote:
>> Hi,
>>
>> thanks for sending a v2.
>>
>> On 11/13/23 19:42, Abhinav Singh wrote:
>>> This patch fixes a sparse warning with this message
>>> "warning:dereference of noderef expression". In this context it means we
>>> are dereferencing a __rcu tagged pointer directly.
>>
>> Better use imperative here, e.g. "Fix a sparse warning ...".
>>
>> Wouldn't ask you to send a v3 for that alone...
>>
>>>
>>> We should not be directly dereferencing a rcu pointer, rather we should
>>> be using rcu helper function rcu_dereferece() inside rcu read critical
>>> section to get a normal pointer which can be dereferenced.
>>
>> ...but this doesn't seem accurate anymore as well.
>>
>> - Danilo
>>
>>>
>>> I tested with qemu with this command
>>> qemu-system-x86_64 \
>>> -m 2G \
>>> -smp 2 \
>>> -kernel bzImage \
>>> -append "console=ttyS0 root=/dev/sda earlyprintk=serial net.ifnames=0" \
>>> -drive file=bullseye.img,format=raw \
>>> -net user,host=10.0.2.10,hostfwd=tcp:127.0.0.1:10021-:22 \
>>> -net nic,model=e1000 \
>>> -enable-kvm \
>>> -nographic \
>>> -pidfile vm.pid \
>>> 2>&1 | tee vm.log
>>> with lockdep enabled.
>>>
>>> Signed-off-by: Abhinav Singh <singhabhinav9051571833@gmail.com>
>>> ---
>>> v1 -> v2 : Replaced the rcu_dereference(...) with unrcu_pointer(...) and
>>> also removed the rcu locking and unlocking function call.
>>>
>>> drivers/gpu/drm/nouveau/nv04_fence.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/nouveau/nv04_fence.c b/drivers/gpu/drm/nouveau/nv04_fence.c
>>> index 5b71a5a5cd85..cdbc75e3d1f6 100644
>>> --- a/drivers/gpu/drm/nouveau/nv04_fence.c
>>> +++ b/drivers/gpu/drm/nouveau/nv04_fence.c
>>> @@ -39,7 +39,7 @@ struct nv04_fence_priv {
>>> static int
>>> nv04_fence_emit(struct nouveau_fence *fence)
>>> {
>>> - struct nvif_push *push = fence->channel->chan.push;
>>> + struct nvif_push *push = unrcu_pointer(fence->channel)->chan.push;
>>> int ret = PUSH_WAIT(push, 2);
>>> if (ret == 0) {
>>> PUSH_NVSQ(push, NV_SW, 0x0150, fence->base.seqno);
>>
> Hi maintainers thanks a lot for reviewing this patch.
> I think I should fix my mistake by sending in another patch so that the code changes and description matches. So should I send another patch ?
Yes, please send a v3.
>
> Thank You,
> Abhinav Singh
>
next prev parent reply other threads:[~2023-11-13 19:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 8:10 [PATCH] " Abhinav Singh
2023-11-13 8:24 ` Maarten Lankhorst
2023-11-13 17:10 ` Danilo Krummrich
2023-11-13 18:37 ` [PATCH v2] drivers: gpu: Fixing warning directly dereferencing a rcu pointer v2 Abhinav Singh
2023-11-13 18:42 ` [PATCH v2] driver: gpu: Fixing warning directly dereferencing a rcu pointer Abhinav Singh
2023-11-13 18:49 ` Danilo Krummrich
2023-11-13 18:55 ` Abhinav Singh
2023-11-13 19:00 ` Danilo Krummrich [this message]
2023-11-13 19:13 ` [PATCH v3] " Abhinav Singh
2023-11-13 19:31 ` Abhinav Singh
2023-11-21 1:20 ` Danilo Krummrich
2023-11-21 8:59 ` Abhinav Singh
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=8e9efe54-2799-4539-a8b0-aa199f8052f6@redhat.com \
--to=dakr@redhat.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=singhabhinav9051571833@gmail.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®