All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alice Ryhl <aliceryhl@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kernel test robot <lkp@intel.com>,
	oe-kbuild-all@lists.linux.dev,  linux-kernel@vger.kernel.org,
	rust-for-linux@vger.kernel.org
Subject: Re: error[E0560]: struct `bindings::file_operations` has no field named `compat_ioctl`
Date: Mon, 1 Dec 2025 10:05:23 +0000	[thread overview]
Message-ID: <aS1oY_RE06wPmaOR@google.com> (raw)
In-Reply-To: <202511300859.35d9m0hj-lkp@intel.com>

On Sun, Nov 30, 2025 at 08:47:52AM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   6bda50f4333fa61c07f04f790fdd4e2c9f4ca610
> commit: f893691e742688ae21ad597c5bba13bef54706cd rust: miscdevice: add base miscdevice abstraction
> date:   1 year, 2 months ago
> config: arm64-randconfig-r073-20251130 (https://download.01.org/0day-ci/archive/20251130/202511300859.35d9m0hj-lkp@intel.com/config)
> compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project b3428bb966f1de8aa48375ffee0eba04ede133b7)
> rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251130/202511300859.35d9m0hj-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/202511300859.35d9m0hj-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
> >> error[E0560]: struct `bindings::file_operations` has no field named `compat_ioctl`
>    --> rust/kernel/miscdevice.rs:161:13
>        |
>    161 |             compat_ioctl: if T::HAS_COMPAT_IOCTL {
>        |             ^^^^^^^^^^^^ `bindings::file_operations` does not have this field
>        |
>    = note: available fields are: `_address`

Hmm, that's weird.  Use of compat_ioctl in this file is guarded behind
CONFIG_COMPAT, which should be sufficient. And this doesn't seem to just
be another UML failure.

Any ideas?

Alice

      reply	other threads:[~2025-12-01 10:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-30  0:47 error[E0560]: struct `bindings::file_operations` has no field named `compat_ioctl` kernel test robot
2025-12-01 10:05 ` Alice Ryhl [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=aS1oY_RE06wPmaOR@google.com \
    --to=aliceryhl@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rust-for-linux@vger.kernel.org \
    /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.