From: Steve French <smfrench@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: Compile warning with current kernel and netfs
Date: Mon, 10 May 2021 22:30:16 -0500 [thread overview]
Message-ID: <CAH2r5mtLY6CRT2CYR--ETq4zPT87+3Eqmk-2=q7eqP+i6BoCLQ@mail.gmail.com> (raw)
In-Reply-To: <CAH2r5ms+NL=J2Wa=wY2doV450qL8S97gnJW_4eSCp1aiz1SEZA@mail.gmail.com>
And forgot to mention that this is on very recent distro, has recent
libraries etc., I had to move to Ubuntu 21.04 due to dependencies of
eBPF and other pieces on newer libc, pahole etc
On Mon, May 10, 2021 at 9:01 PM Steve French <smfrench@gmail.com> wrote:
>
> Noticed the following netfs related new warning when compiling cifs.ko
> with the current 5.13-rc1
>
> CC [M] /home/smfrench/cifs-2.6/fs/cifs/fscache.o
> CHECK /home/smfrench/cifs-2.6/fs/cifs/fscache.c
> /home/smfrench/cifs-2.6/fs/cifs/fscache.c: note: in included file
> (through include/linux/fscache.h,
> /home/smfrench/cifs-2.6/fs/cifs/fscache.h):
> ./include/linux/netfs.h:93:15: error: don't know how to apply mode to
> unsigned int enum netfs_read_source
> CC [M] /home/smfrench/cifs-2.6/fs/cifs/cache.o
> CHECK /home/smfrench/cifs-2.6/fs/cifs/cache.c
> /home/smfrench/cifs-2.6/fs/cifs/cache.c: note: in included file
> (through include/linux/fscache.h,
> /home/smfrench/cifs-2.6/fs/cifs/fscache.h):
> ./include/linux/netfs.h:93:15: error: don't know how to apply mode to
> unsigned int enum netfs_read_source
>
> It doesn't like this enum in include/linux/netfs.h:
>
> enum netfs_read_source {
> NETFS_FILL_WITH_ZEROES,
> NETFS_DOWNLOAD_FROM_SERVER,
> NETFS_READ_FROM_CACHE,
> NETFS_INVALID_READ,
> } __mode(byte);
>
> --
> Thanks,
>
> Steve
--
Thanks,
Steve
next prev parent reply other threads:[~2021-05-11 3:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 2:01 Compile warning with current kernel and netfs Steve French
2021-05-11 2:07 ` Matthew Wilcox
2021-05-11 3:28 ` Steve French
2021-05-11 3:30 ` Steve French [this message]
2021-05-11 13:03 ` David Howells
2021-05-11 19:41 ` Steve French
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='CAH2r5mtLY6CRT2CYR--ETq4zPT87+3Eqmk-2=q7eqP+i6BoCLQ@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@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 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).