From: Christoph Hellwig <hch@lst.de>
To: Paul Moore <paul@paul-moore.com>
Cc: Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
Eric Paris <eparis@parisplace.org>,
linux-s390@vger.kernel.org, linux-fsdevel@vger.kernel.org,
selinux@vger.kernel.org
Subject: Re: sb->s_fs_info freeing fixes
Date: Thu, 31 Aug 2023 16:39:47 +0200 [thread overview]
Message-ID: <20230831143947.GA16365@lst.de> (raw)
In-Reply-To: <CAHC9VhQOpy=rLNmirT7afkEdf5_PRnLVsdPJQvxqaF0G4JrCgQ@mail.gmail.com>
On Thu, Aug 31, 2023 at 10:38:09AM -0400, Paul Moore wrote:
> No need to change anything in this case, but in the future if there
> are no patch dependency or ordering issues can you let me take the
> SELinux patches via the SELinux tree? It helps prevent merge
> conflicts during the next merge window and quiets the daily automated
> checks I have in place to detect SELinux changes outside of the
> SELinux tree.
Even if this goes into the next merge window we'd need it in the vfs
tree as it is preparation for other work on VFS interfaces.
next prev parent reply other threads:[~2023-08-31 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 5:31 sb->s_fs_info freeing fixes Christoph Hellwig
2023-08-31 5:31 ` [PATCH 1/4] ramfs: free sb->s_fs_info after shutting down the super block Christoph Hellwig
2023-08-31 6:25 ` Al Viro
2023-08-31 5:31 ` [PATCH 2/4] devpts: " Christoph Hellwig
2023-08-31 6:31 ` Al Viro
2023-08-31 5:31 ` [PATCH 3/4] selinuxfs: " Christoph Hellwig
2023-08-31 6:33 ` Al Viro
2023-08-31 5:31 ` [PATCH 4/4] hypfs: " Christoph Hellwig
2023-08-31 6:37 ` Al Viro
2023-08-31 10:20 ` sb->s_fs_info freeing fixes Christian Brauner
2023-08-31 10:29 ` Christian Brauner
2023-08-31 12:36 ` Christoph Hellwig
2023-08-31 13:11 ` Christian Brauner
2023-08-31 14:38 ` Paul Moore
2023-08-31 14:39 ` Christoph Hellwig [this message]
2023-08-31 14:49 ` Paul Moore
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=20230831143947.GA16365@lst.de \
--to=hch@lst.de \
--cc=agordeev@linux.ibm.com \
--cc=brauner@kernel.org \
--cc=eparis@parisplace.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).