From: Saket Kumar Bhaskar <skb99@linux.ibm.com>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Cc: Hari Bathini <hbathini@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
bpf <bpf@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [linux-next] selftests/bpf fails to build
Date: Fri, 9 May 2025 17:40:00 +0530 [thread overview]
Message-ID: <aB3wmPosqkyNL749@linux.ibm.com> (raw)
In-Reply-To: <e915da49-2b9a-4c4c-a34f-877f378129f6@linux.ibm.com>
On Fri, May 09, 2025 at 05:32:51PM +0530, Venkat Rao Bagalkote wrote:
> Hello,
>
>
> I am observing selftests/bpf fails to build on the next-20250508 kernel.
>
>
> Errors:
>
>
> GEN
> /root/linux-next/tools/testing/selftests/bpf/tools/build/bpftool/vmlinux.h
> bpf_testmod.c:494:17: error: initialization of 'ssize_t (*)(struct file *,
> struct kobject *, const struct bin_attribute *, char *, loff_t, size_t)'
> {aka 'long int (*)(struct file *, struct kobject *, const struct
> bin_attribute *, char *, long long int, long unsigned int)'} from
> incompatible pointer type 'ssize_t (*)(struct file *, struct kobject *,
> struct bin_attribute *, char *, loff_t, size_t)' {aka 'long int (*)(struct
> file *, struct kobject *, struct bin_attribute *, char *, long long int,
> long unsigned int)'} [-Wincompatible-pointer-types]
> 494 | .read = bpf_testmod_test_read,
> | ^~~~~~~~~~~~~~~~~~~~~
> bpf_testmod.c:494:17: note: (near initialization for
> 'bin_attr_bpf_testmod_file.read')
> bpf_testmod.c:495:18: error: initialization of 'ssize_t (*)(struct file *,
> struct kobject *, const struct bin_attribute *, char *, loff_t, size_t)'
> {aka 'long int (*)(struct file *, struct kobject *, const struct
> bin_attribute *, char *, long long int, long unsigned int)'} from
> incompatible pointer type 'ssize_t (*)(struct file *, struct kobject *,
> struct bin_attribute *, char *, loff_t, size_t)' {aka 'long int (*)(struct
> file *, struct kobject *, struct bin_attribute *, char *, long long int,
> long unsigned int)'} [-Wincompatible-pointer-types]
> 495 | .write = bpf_testmod_test_write,
> | ^~~~~~~~~~~~~~~~~~~~~~
> bpf_testmod.c:495:18: note: (near initialization for
> 'bin_attr_bpf_testmod_file.write')
> make[4]: *** [/root/linux-next/scripts/Makefile.build:203: bpf_testmod.o]
> Error 1
> make[3]: *** [/root/linux-next/Makefile:2009: .] Error 2
> make[2]: *** [Makefile:248: __sub-make] Error 2
> make[1]: *** [Makefile:18: all] Error 2
> make: *** [Makefile:282: test_kmods/bpf_testmod.ko] Error 2
> make: *** Waiting for unfinished jobs...
>
>
> If you happen to fix this, please add below tag.
>
>
> Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
>
>
>
> Regards,
>
> Venkat.
>
Hi Venkat, thanks for reporting this. This is due to Commit
97d06802d10a ("sysfs: constify bin_attribute argument of bin_attribute::read/write()")
that changed the required type for struct bin_attribute to const struct bin_attribute.
Will send out a patch to fix this, shortly.
Thanks,
Saket
prev parent reply other threads:[~2025-05-09 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 12:02 [linux-next] selftests/bpf fails to build Venkat Rao Bagalkote
2025-05-09 12:10 ` Saket Kumar Bhaskar [this message]
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=aB3wmPosqkyNL749@linux.ibm.com \
--to=skb99@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=hbathini@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=venkat88@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).