From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: selinux@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] SELinux fixes for v5.19 (#1)
Date: Thu, 16 Jun 2022 17:47:44 -0400 [thread overview]
Message-ID: <CAHC9VhQFi51nuyMXGaJcYcyQT89tMcizSEVGf39hDaf89QffNA@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhQa-L-_F4UdMekqvyF714xhEerVQzc9rPvuwTQJtmMd8A@mail.gmail.com>
On Thu, Jun 16, 2022 at 5:44 PM Paul Moore <paul@paul-moore.com> wrote:
>
> Linus,
>
> A single SELinux patch to fix memory leaks when mounting filesystems
> with SELinux mount options. Please merge for v5.19.
>
> Thanks,
> -Paul
>
> --
> The following changes since commit b13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3:
>
> Linux 5.19-rc2 (2022-06-12 16:11:37 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git
> selinux-pr-20220616
... that is obviously not the SELinux tree, although it does somewhat
hint that you're also going to see an audit PR in just a moment too.
Here is the proper SELinux tree:
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
selinux-pr-20220616
Sorry for the mixup.
> for you to fetch changes up to cad140d00899e7a9cb6fe93b282051df589e671c:
>
> selinux: free contexts previously transferred in selinux_add_opt()
> (2022-06-15 21:20:45 -0400)
>
> ----------------------------------------------------------------
> selinux/stable-5.19 PR 20220616
>
> ----------------------------------------------------------------
> Christian Göttsche (1):
> selinux: free contexts previously transferred in selinux_add_opt()
>
> security/selinux/hooks.c | 11 ++++-------
> 1 file changed, 4 insertions(+), 7 deletions(-)
--
paul-moore.com
next prev parent reply other threads:[~2022-06-16 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 21:44 [GIT PULL] SELinux fixes for v5.19 (#1) Paul Moore
2022-06-16 21:47 ` Paul Moore [this message]
2022-06-16 22:57 ` pr-tracker-bot
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=CAHC9VhQFi51nuyMXGaJcYcyQT89tMcizSEVGf39hDaf89QffNA@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.