From: "Theodore Ts'o" <tytso@mit.edu>
To: Arnd Bergmann <arnd@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
Hugh Dickins <hughd@google.com>,
clang-built-linux <llvm@lists.linux.dev>,
kbuild-all@lists.01.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH] mm/shmem: add support for FS_IOC_[SG]ETFLAGS for tmpfs
Date: Fri, 15 Jul 2022 07:36:57 -0400 [thread overview]
Message-ID: <YtFRWXzLUjGQ5bD9@mit.edu> (raw)
In-Reply-To: <CAK8P3a1zoKAhfZ+zoukwUTFbi9LYdVPFR7wMJ47WSOQ5zNVMRQ@mail.gmail.com>
On Fri, Jul 15, 2022 at 01:09:04PM +0200, Arnd Bergmann wrote:
> On Fri, Jul 15, 2022 at 1:01 AM kernel test robot <lkp@intel.com> wrote:
> >
> > >> mm/shmem.c:1062:22: error: use of undeclared identifier 'EXT2_APPEND_FL'
> > if (info->fsflags & EXT2_APPEND_FL)
> > ^
> > >> mm/shmem.c:1064:22: error: use of undeclared identifier 'EXT2_IMMUTABLE_FL'
> > if (info->fsflags & EXT2_IMMUTABLE_FL)
> > ^
> > >> mm/shmem.c:1066:22: error: use of undeclared identifier 'EXT2_NODUMP_FL'
> > if (info->fsflags & EXT2_NODUMP_FL)
> > ^
>
> I suppose this just needs to use FS_APPEND_FL/FS_IMMUTABLE_FL/FS_NODUMP_FL
> instead of the ext2 alias names?
The zero day bot was testing the v1 version of the patch. This was
fixed in the -v2 and -v3 versions.
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: Theodore Ts'o <tytso@mit.edu>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] mm/shmem: add support for FS_IOC_[SG]ETFLAGS for tmpfs
Date: Fri, 15 Jul 2022 07:36:57 -0400 [thread overview]
Message-ID: <YtFRWXzLUjGQ5bD9@mit.edu> (raw)
In-Reply-To: <CAK8P3a1zoKAhfZ+zoukwUTFbi9LYdVPFR7wMJ47WSOQ5zNVMRQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On Fri, Jul 15, 2022 at 01:09:04PM +0200, Arnd Bergmann wrote:
> On Fri, Jul 15, 2022 at 1:01 AM kernel test robot <lkp@intel.com> wrote:
> >
> > >> mm/shmem.c:1062:22: error: use of undeclared identifier 'EXT2_APPEND_FL'
> > if (info->fsflags & EXT2_APPEND_FL)
> > ^
> > >> mm/shmem.c:1064:22: error: use of undeclared identifier 'EXT2_IMMUTABLE_FL'
> > if (info->fsflags & EXT2_IMMUTABLE_FL)
> > ^
> > >> mm/shmem.c:1066:22: error: use of undeclared identifier 'EXT2_NODUMP_FL'
> > if (info->fsflags & EXT2_NODUMP_FL)
> > ^
>
> I suppose this just needs to use FS_APPEND_FL/FS_IMMUTABLE_FL/FS_NODUMP_FL
> instead of the ext2 alias names?
The zero day bot was testing the v1 version of the patch. This was
fixed in the -v2 and -v3 versions.
- Ted
next prev parent reply other threads:[~2022-07-15 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 14:52 [PATCH] mm/shmem: add support for FS_IOC_[SG]ETFLAGS for tmpfs Theodore Ts'o
2022-07-13 19:11 ` Andrew Morton
2022-07-14 1:40 ` Theodore Ts'o
2022-07-14 2:24 ` [PATCH -v2] mm/shmem: support FS_IOC_[SG]ETFLAGS in tmpfs Theodore Ts'o
2022-07-15 1:59 ` [PATCH -v3] " Theodore Ts'o
2022-07-20 11:10 ` Theodore Ts'o
2022-07-20 16:59 ` Andrew Morton
2022-08-11 4:44 ` Hugh Dickins
2022-07-14 23:01 ` [PATCH] mm/shmem: add support for FS_IOC_[SG]ETFLAGS for tmpfs kernel test robot
2022-07-15 11:09 ` Arnd Bergmann
2022-07-15 11:09 ` Arnd Bergmann
2022-07-15 11:36 ` Theodore Ts'o [this message]
2022-07-15 11:36 ` Theodore Ts'o
2022-07-14 23:11 ` kernel test robot
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=YtFRWXzLUjGQ5bD9@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=arnd@kernel.org \
--cc=hughd@google.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/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.