From: kernel test robot <lkp@intel.com>
To: Fedor Pchelkin <pchelkin@ispras.ru>, Theodore Ts'o <tytso@mit.edu>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Fedor Pchelkin <pchelkin@ispras.ru>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jan Kara <jack@suse.cz>, "Darrick J. Wong" <djwong@kernel.org>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Kees Cook <kees@kernel.org>,
lvc-project@linuxtesting.org
Subject: Re: [PATCH 1/2] ext4: fix up copying of mount_opts in superblock tuning ioctls
Date: Wed, 29 Oct 2025 18:54:54 +0800 [thread overview]
Message-ID: <202510291846.pFj7PlQQ-lkp@intel.com> (raw)
In-Reply-To: <20251028130949.599847-1-pchelkin@ispras.ru>
Hi Fedor,
kernel test robot noticed the following build errors:
[auto build test ERROR on tytso-ext4/dev]
[also build test ERROR on linus/master v6.18-rc3 next-20251029]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Fedor-Pchelkin/ext4-fix-string-copying-in-parse_apply_sb_mount_options/20251028-211235
base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
patch link: https://lore.kernel.org/r/20251028130949.599847-1-pchelkin%40ispras.ru
patch subject: [PATCH 1/2] ext4: fix up copying of mount_opts in superblock tuning ioctls
config: x86_64-buildonly-randconfig-002-20251029 (https://download.01.org/0day-ci/archive/20251029/202510291846.pFj7PlQQ-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251029/202510291846.pFj7PlQQ-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/202510291846.pFj7PlQQ-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from <built-in>:1:
>> ./usr/include/linux/ext4.h:141:22: error: expected ';' at end of declaration list
141 | __u8 mount_opts[64] __nonstring;
| ^
| ;
1 error generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-29 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 13:09 [PATCH 1/2] ext4: fix up copying of mount_opts in superblock tuning ioctls Fedor Pchelkin
2025-10-28 13:09 ` [PATCH 2/2] ext4: fix string copying in parse_apply_sb_mount_options() Fedor Pchelkin
2025-10-28 13:32 ` Fedor Pchelkin
2025-10-29 9:22 ` [PATCH 1/2] ext4: fix up copying of mount_opts in superblock tuning ioctls kernel test robot
2025-10-29 9:47 ` Fedor Pchelkin
2025-10-29 10:54 ` kernel test robot [this message]
2025-10-30 11:32 ` Jan Kara
2025-10-31 15:44 ` Fedor Pchelkin
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=202510291846.pFj7PlQQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=adilger.kernel@dilger.ca \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=kees@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lvc-project@linuxtesting.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pchelkin@ispras.ru \
--cc=tytso@mit.edu \
/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