[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3349244.1662480110@warthog.procyon.org.uk>
Date: Tue, 06 Sep 2022 17:01:50 +0100
From: David Howells <dhowells@...hat.com>
To: Jeff Layton <jlayton@...nel.org>
Cc: dhowells@...hat.com, viro@...iv.linux.org.uk,
Trond Myklebust <trond.myklebust@...merspace.com>,
Anna Schumaker <anna@...nel.org>,
Scott Mayhew <smayhew@...hat.com>,
Paul Moore <paul@...l-moore.com>,
Casey Schaufler <casey@...aufler-ca.com>,
linux-nfs@...r.kernel.org, selinux@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org, dwysocha@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5] vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing
Jeff Layton <jlayton@...nel.org> wrote:
> If this or the other allocations below fail, do you need to free the
> prior ones here? Or do they automagically get cleaned up somehow?
Once the fs_context is allocated, it will always get cleaned up with
put_fs_context(), which will dispose of the partially constructed
smack_mnt_opts struct.
David
Powered by blists - more mailing lists