From: bill.c.roberts@gmail.com (William Roberts)
To: linux-security-module@vger.kernel.org
Subject: Can we delete audit_log_secctx()?
Date: Fri, 20 Oct 2017 18:05:56 -0700 [thread overview]
Message-ID: <CAFftDdq7ED6w=56mY3rcytMRWqSSN16H56nUW5cq8qdLvJEoEA@mail.gmail.com> (raw)
In-Reply-To: <1969680b-0239-e6fb-eebd-199467596306@schaufler-ca.com>
On Fri, Oct 20, 2017 at 3:16 PM, Casey Schaufler <casey@schaufler-ca.com> wrote:
> The function audit_log_secctx() is unused and cannot be
> made safe for the stacked/namespaced security module case.
> It, alas, shows up in the KAPI. Can this derelict code be
> removed? I'll provide a patch it it can go.
It seems to be unused...
http://elixir.free-electrons.com/linux/v4.14-rc5/ident/audit_log_secctx
>
> --
> Linux-audit mailing list
> Linux-audit at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
--
Respectfully,
William C Roberts
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: William Roberts <bill.c.roberts@gmail.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Paul Moore <paul@paul-moore.com>,
Linux Audit <linux-audit@redhat.com>,
LSM <linux-security-module@vger.kernel.org>
Subject: Re: Can we delete audit_log_secctx()?
Date: Fri, 20 Oct 2017 18:05:56 -0700 [thread overview]
Message-ID: <CAFftDdq7ED6w=56mY3rcytMRWqSSN16H56nUW5cq8qdLvJEoEA@mail.gmail.com> (raw)
In-Reply-To: <1969680b-0239-e6fb-eebd-199467596306@schaufler-ca.com>
On Fri, Oct 20, 2017 at 3:16 PM, Casey Schaufler <casey@schaufler-ca.com> wrote:
> The function audit_log_secctx() is unused and cannot be
> made safe for the stacked/namespaced security module case.
> It, alas, shows up in the KAPI. Can this derelict code be
> removed? I'll provide a patch it it can go.
It seems to be unused...
http://elixir.free-electrons.com/linux/v4.14-rc5/ident/audit_log_secctx
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
--
Respectfully,
William C Roberts
next prev parent reply other threads:[~2017-10-21 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 22:16 Can we delete audit_log_secctx()? Casey Schaufler
2017-10-20 22:16 ` Casey Schaufler
2017-10-21 1:05 ` William Roberts [this message]
2017-10-21 1:05 ` William Roberts
2017-10-23 23:14 ` Paul Moore
2017-10-23 23:14 ` 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='CAFftDdq7ED6w=56mY3rcytMRWqSSN16H56nUW5cq8qdLvJEoEA@mail.gmail.com' \
--to=bill.c.roberts@gmail.com \
--cc=linux-security-module@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.