mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Maíra Canal" <mcanal@igalia.com>
To: Christian Gmeiner <christian.gmeiner@gmail.com>,
	Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: linux-hexagon@vger.kernel.org, bcain@quicinc.com,
	linux-kernel@vger.kernel.org, dhowells@redhat.com,
	edumazet@google.com, Willem de Bruijn <willemb@google.com>,
	kernel test robot <lkp@intel.com>,
	mcanal@igalia.com
Subject: Re: [PATCH] hexagon: fix using plain integer as NULL pointer warning in cmpxchg
Date: Sun, 26 Jan 2025 19:59:00 -0300	[thread overview]
Message-ID: <b0504158-e9e2-4f00-8a9a-a653a6a0e313@igalia.com> (raw)
In-Reply-To: <CAH9NwWdODq0GXWJb_4jQNhgWjjAYfZccGLLLe7a=LVC95ew2tQ@mail.gmail.com>

Hi Brian,

Do you have an estimate for when this patch will be picked? We are 
getting build reports from Hexagon in the V3D GPU driver [1].

[1] 
https://lore.kernel.org/oe-kbuild-all/202501031246.AD8Jjze0-lkp@intel.com/

Best Regards,
- Maíra

On 07/01/25 07:17, Christian Gmeiner wrote:
> Hi Willem,
> 
>>
>> From: Willem de Bruijn <willemb@google.com>
>>
>> Sparse reports
>>
>>      net/ipv4/inet_diag.c:1511:17: sparse: sparse: Using plain integer as NULL pointer
>>
>> Due to this code calling cmpxchg on a non-integer type
>> struct inet_diag_handler *
>>
>>      return !cmpxchg((const struct inet_diag_handler**)&inet_diag_table[type],
>>                      NULL, h) ? 0 : -EEXIST;
>>
>> While hexagon's cmpxchg assigns an integer value to a variable of this
>> type.
>>
>>      __typeof__(*(ptr)) __oldval = 0;
>>
>> Update this assignment to cast 0 to the correct type.
>>
>> The original issue is easily reproduced at head with the below block,
>> and is absent after this change.
>>
>>      make LLVM=1 ARCH=hexagon defconfig
>>      make C=1 LLVM=1 ARCH=hexagon net/ipv4/inet_diag.o
>>
>> Fixes: 99a70aa051d2 ("Hexagon: Add processor and system headers")
>> Reported-by: kernel test robot <lkp@intel.com>
>> Closes: https://lore.kernel.org/oe-kbuild-all/202411091538.PGSTqUBi-lkp@intel.com/
>> Signed-off-by: Willem de Bruijn <willemb@google.com>
> 
> Closes: https://lore.kernel.org/oe-kbuild-all/202501031246.AD8Jjze0-lkp@intel.com/
> Tested-by: Christian Gmeiner <cgmeiner@igalia.com>
> 
>> ---
>>   arch/hexagon/include/asm/cmpxchg.h | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/hexagon/include/asm/cmpxchg.h b/arch/hexagon/include/asm/cmpxchg.h
>> index bf6cf5579cf4..9c58fb81f7fd 100644
>> --- a/arch/hexagon/include/asm/cmpxchg.h
>> +++ b/arch/hexagon/include/asm/cmpxchg.h
>> @@ -56,7 +56,7 @@ __arch_xchg(unsigned long x, volatile void *ptr, int size)
>>          __typeof__(ptr) __ptr = (ptr);                          \
>>          __typeof__(*(ptr)) __old = (old);                       \
>>          __typeof__(*(ptr)) __new = (new);                       \
>> -       __typeof__(*(ptr)) __oldval = 0;                        \
>> +       __typeof__(*(ptr)) __oldval = (__typeof__(*(ptr))) 0;   \
>>                                                                  \
>>          asm volatile(                                           \
>>                  "1:     %0 = memw_locked(%1);\n"                \
>> --
>> 2.47.0.338.g60cca15819-goog
>>
>>
> 
> 


  reply	other threads:[~2025-01-26 22:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 22:17 Willem de Bruijn
2025-01-07 10:17 ` Christian Gmeiner
2025-01-26 22:59   ` Maíra Canal [this message]
2025-01-27 16:21     ` Brian Cain

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=b0504158-e9e2-4f00-8a9a-a653a6a0e313@igalia.com \
    --to=mcanal@igalia.com \
    --cc=bcain@quicinc.com \
    --cc=christian.gmeiner@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@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®