From: Heiko Carstens <hca@linux.ibm.com>
To: kernel test robot <lkp@intel.com>
Cc: Andrey Albershteyn <aalbersh@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Matt Turner <mattst88@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Michal Simek <monstr@monstr.eu>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
Helge Deller <deller@gmx.de>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Naveen N Rao <naveen@kernel.org>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
"David S. Miller" <davem@davemloft.net>,
Andreas Larsson <andreas@gaisler.com>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org
Subject: Re: [PATCH v5 7/7] fs: introduce file_getattr and file_setattr syscalls
Date: Mon, 19 May 2025 10:06:59 +0200 [thread overview]
Message-ID: <20250519080659.11601Ae4-hca@linux.ibm.com> (raw)
In-Reply-To: <202505181900.UGh2tVRs-lkp@intel.com>
On Sun, May 18, 2025 at 07:26:00PM +0800, kernel test robot wrote:
> Hi Andrey,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on 0d8d44db295ccad20052d6301ef49ff01fb8ae2d]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Andrey-Albershteyn/fs-split-fileattr-related-helpers-into-separate-file/20250513-172128
> base: 0d8d44db295ccad20052d6301ef49ff01fb8ae2d
> patch link: https://lore.kernel.org/r/20250513-xattrat-syscall-v5-7-22bb9c6c767f%40kernel.org
> patch subject: [PATCH v5 7/7] fs: introduce file_getattr and file_setattr syscalls
> config: s390-randconfig-r112-20250518 (https://download.01.org/0day-ci/archive/20250518/202505181900.UGh2tVRs-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 8.5.0
> reproduce: (https://download.01.org/0day-ci/archive/20250518/202505181900.UGh2tVRs-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202505181900.UGh2tVRs-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> >> fs/file_attr.c:362:1: sparse: sparse: Using plain integer as NULL pointer
> >> fs/file_attr.c:362:1: sparse: sparse: Using plain integer as NULL pointer
> >> fs/file_attr.c:362:1: sparse: sparse: Using plain integer as NULL pointer
> >> fs/file_attr.c:362:1: sparse: sparse: Using plain integer as NULL pointer
> fs/file_attr.c:416:1: sparse: sparse: Using plain integer as NULL pointer
> fs/file_attr.c:416:1: sparse: sparse: Using plain integer as NULL pointer
> fs/file_attr.c:416:1: sparse: sparse: Using plain integer as NULL pointer
> fs/file_attr.c:416:1: sparse: sparse: Using plain integer as NULL pointer
>
> vim +362 fs/file_attr.c
>
> 361
> > 362 SYSCALL_DEFINE5(file_getattr, int, dfd, const char __user *, filename,
> 363 struct fsxattr __user *, ufsx, size_t, usize,
> 364 unsigned int, at_flags)
> 365 {
Please ignore the warning. There is nothing to fix; this is a warning which
happens only with CONFIG_COMPAT and Al's "SC_DELOUSE" macro, which is used for
compat syscalls. Sparse cannot handle that.
prev parent reply other threads:[~2025-05-19 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250513-xattrat-syscall-v5-7-22bb9c6c767f@kernel.org>
2025-05-13 22:39 ` [PATCH v5 7/7] fs: introduce file_getattr and file_setattr syscalls kernel test robot
2025-05-18 11:26 ` kernel test robot
2025-05-19 8:06 ` Heiko Carstens [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=20250519080659.11601Ae4-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=aalbersh@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=andreas@gaisler.com \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dalias@libc.org \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gor@linux.ibm.com \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=luto@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mattst88@gmail.com \
--cc=mingo@redhat.com \
--cc=monstr@monstr.eu \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard.henderson@linaro.org \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=will@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).