[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1596937.1589907073@warthog.procyon.org.uk>
Date: Tue, 19 May 2020 17:51:13 +0100
From: David Howells <dhowells@...hat.com>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: dhowells@...hat.com, Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
Al Viro <viro@...IV.linux.org.uk>
Subject: Re: linux-next: Tree for May 12 (fs/namespace.c)
Randy Dunlap <rdunlap@...radead.org> wrote:
> CC fs/namespace.o
> ../fs/namespace.c: In function "fsinfo_generic_mount_topology":
> ../fs/namespace.c:4274:42: error: "struct mount" has no member named "mnt_topology_changes"
> p->mnt_topology_changes = atomic_read(&m->mnt_topology_changes);
> ^~
>
> i.e., CONFIG_MOUNT_NOTIFICATIONS is not set/enabled.
All the accesses to struct mount::mnt_topology_changes should now be wrapped
in #ifdef CONFIG_MOUNT_NOTIFICATIONS.
David
Powered by blists - more mailing lists