linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: paul@paul-moore.com
Cc: netdev@vger.kernel.org, selinux@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	stephen.smalley.work@gmail.com
Subject: Re: [net-next PATCH] netlabel: fix problems with mapping removal
Date: Fri, 21 Aug 2020 11:38:44 -0700 (PDT)	[thread overview]
Message-ID: <20200821.113844.1413413632075759126.davem@davemloft.net> (raw)
In-Reply-To: <159797437409.20181.15427109610194880479.stgit@sifl>

From: Paul Moore <paul@paul-moore.com>
Date: Thu, 20 Aug 2020 21:46:14 -0400

> This patch fixes two main problems seen when removing NetLabel
> mappings: memory leaks and potentially extra audit noise.

These are bug fixes therefore this needs to target the 'net' tree
and you must also provide appropriate "Fixes:" tags.

Thank you.

  reply	other threads:[~2020-08-21 18:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21  1:46 [net-next PATCH] netlabel: fix problems with mapping removal Paul Moore
2020-08-21 18:38 ` David Miller [this message]
2020-08-21 20:36   ` 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=20200821.113844.1413413632075759126.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-security-module@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley.work@gmail.com \
    /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).