From: Paul Moore <paul@paul-moore.com>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: SElinux list <selinux@vger.kernel.org>
Subject: Re: [PATCH] selinux: SCTP fixes, including ASCONF
Date: Mon, 15 Aug 2022 16:56:16 -0400 [thread overview]
Message-ID: <CAHC9VhSTg1BZNF86SjH0uzyuwp5_wpaB_BKvyWML4k+7aTt0YA@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhRpTR_zdj+cdeGGKoe1vZKBy4FK4JP6iyurXR0NOr2tXw@mail.gmail.com>
On Thu, Aug 11, 2022 at 11:04 AM Paul Moore <paul@paul-moore.com> wrote:
> On Thu, Aug 11, 2022 at 6:03 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > On Wed, Aug 10, 2022 at 12:14 AM Paul Moore <paul@paul-moore.com> wrote:
...
> > I believe you forgot to modify also
> > selinux_netlbl_sctp_assoc_request() in a similar fashion as the other
> > functions below?
>
> Good point. I suspect selinux_netlbl_sctp_assoc_request() will be
> greatly simplified too, that will be nice.
I'm beginning to think the SELinux/SCTP code is cursed :/
That change brought up some other issues (more of the
multiple-associations-on-a-single-socket variety) which I need to
think about some more, so I'm putting this on the back-burner for a
little bit while I sort out the io_uring and other things which are
more straightforward and need to get into linux-next ASAP.
--
paul-moore.com
next prev parent reply other threads:[~2022-08-16 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 22:12 [PATCH] selinux: SCTP fixes, including ASCONF Paul Moore
2022-08-11 10:03 ` Ondrej Mosnacek
2022-08-11 15:04 ` Paul Moore
2022-08-15 20:56 ` Paul Moore [this message]
2022-08-23 15:34 ` Ondrej Mosnacek
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=CAHC9VhSTg1BZNF86SjH0uzyuwp5_wpaB_BKvyWML4k+7aTt0YA@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=omosnace@redhat.com \
--cc=selinux@vger.kernel.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.