All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Anubhav Shelat <ashelat@redhat.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Shivank Garg <shivankg@amd.com>,
	Ackerley Tng <ackerleytng@google.com>,
	Fuad Tabba <tabba@google.com>,
	Christian Brauner <brauner@kernel.org>,
	Sean Christopherson <seanjc@google.com>
Subject: Re: [PATCH v3] tracefs: Add read-only eventfs filesystem at /sys/kernel/events
Date: Thu, 20 Aug 2026 19:25:46 +0800	[thread overview]
Message-ID: <202608201957.NHoAQjoy-lkp@intel.com> (raw)
In-Reply-To: <20260810160708.3460a2fd@gandalf.local.home>

Hi Steven,

kernel test robot noticed the following build errors:

[auto build test ERROR on v7.2]
[also build test ERROR on next-20260819]
[cannot apply to trace/for-next linus/master]
[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/Steven-Rostedt/tracefs-Add-read-only-eventfs-filesystem-at-sys-kernel-events/20260810-160708
base:   v7.2
patch link:    https://lore.kernel.org/r/20260810160708.3460a2fd%40gandalf.local.home
patch subject: [PATCH v3] tracefs: Add read-only eventfs filesystem at /sys/kernel/events
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260820/202608201957.NHoAQjoy-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260820/202608201957.NHoAQjoy-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/202608201957.NHoAQjoy-lkp@intel.com/

All errors (new ones prefixed by >>):

>> fs/tracefs/event_inode.c:38:16: error: use of undeclared identifier 'EVENTFS_SUPER_MAGIC'
      38 |         sb->s_magic = EVENTFS_SUPER_MAGIC;
         |                       ^~~~~~~~~~~~~~~~~~~
   1 error generated.


vim +/EVENTFS_SUPER_MAGIC +38 fs/tracefs/event_inode.c

    30	
    31	static int eventfs_ro_fill_super(struct super_block *sb, struct fs_context *fc)
    32	{
    33		struct inode *inode;
    34		struct dentry *root;
    35	
    36		sb->s_blocksize = PAGE_SIZE;
    37		sb->s_blocksize_bits = PAGE_SHIFT;
  > 38		sb->s_magic = EVENTFS_SUPER_MAGIC;
    39		sb->s_op = &eventfs_ro_super_operations;
    40		sb->s_time_gran = 1;
    41		sb->s_flags |= SB_RDONLY;
    42	
    43		inode = new_inode(sb);
    44		if (!inode)
    45			return -ENOMEM;
    46	
    47		inode->i_ino = 1;
    48		inode->i_mode = S_IFDIR | 0555;
    49		simple_inode_init_ts(inode);
    50		inode->i_op = &simple_dir_inode_operations;
    51		inode->i_fop = &simple_dir_operations;
    52		set_nlink(inode, 2);
    53	
    54		set_default_d_op(sb, &tracefs_dentry_operations);
    55	
    56		root = d_make_root(inode);
    57		if (!root)
    58			return -ENOMEM;
    59	
    60		sb->s_root = root;
    61	
    62		return 0;
    63	}
    64	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2026-08-20 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 20:07 [PATCH v3] tracefs: Add read-only eventfs filesystem at /sys/kernel/events Steven Rostedt
2026-08-10 21:39 ` Steven Rostedt
2026-08-11  1:28 ` Masami Hiramatsu
2026-08-11  1:36   ` Steven Rostedt
2026-08-20  5:32 ` kernel test robot
2026-08-20 11:25 ` kernel test robot
2026-08-20 16:31   ` Li, Philip
2026-08-20 11:25 ` kernel test robot [this message]
2026-08-20 16:32   ` Li, Philip

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=202608201957.NHoAQjoy-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ackerleytng@google.com \
    --cc=ashelat@redhat.com \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mhiramat@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=seanjc@google.com \
    --cc=shivankg@amd.com \
    --cc=tabba@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.