SELinux Archive on
 help / color / Atom feed
From: Paul Moore <>
To: Ondrej Mosnacek <>
Cc: Jeff Vander Stoep <>,
	SElinux list <>,
	Stephen Smalley <>,
	Will Deacon <>,
	"Paul E. McKenney" <>,, Jovana Knezevic <>
Subject: Re: [PATCH v9] selinux: sidtab: reverse lookup hash table
Date: Wed, 4 Dec 2019 18:52:21 -0500
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Dec 4, 2019 at 4:11 AM Ondrej Mosnacek <> wrote:
> On Tue, Dec 3, 2019 at 1:33 AM Paul Moore <> wrote:
> > Thanks Jeff, as well as everyone else who contributed reviews and feedback.
> >
> > I've pulled this into a working branch and I'll be merging it with the
> > other sidtab patches before posting it to a "next-queue" branch for
> > review later this week.  When done, I'll send a note to the list, as
> > well as the relevant patch authors; your help in reviewing the merge
> > would be greatly appreciated.
> I tried doing the merge on my own here [1], you can use it as a sanity
> check if we came to the same/similar result. I based it off your
> existing next-queue, which contains only Jeff's patch at the time of
> writing. I only build-tested it so far.

Thanks, that was a good sanity check.  There are some minor diffs from
what I ended up with, but nothing substantive that I can see.

Although I'll be honest, the merge wasn't as bad as I thought it would
be; most of the fuzz was simply due shuffling and renaming of data
structures, which generally isn't too bad.  Although I'm still
building the kernel to test it, so let's see if that statement still
holds (although it looks like it passed Stephen's testing). ;)

If you haven't noticed already, the merge currently lives in the
selinux/next-queue branch; if you notice anything off, feel free to
send a fixup patch.

> Note that there are two whitespace cleanups included in the string
> cache commit that I intuitively did while resolving the merge
> conflicts. You might want to move those to the first commit or just
> ignore them.

When looking at the combined diff between the two sidtab patches and
comparing it to your merge I did make a few additional small cosmetic
tweaks.  Assuming the testing goes well, I'll probably go over
everything one more time to make sure the style looks okay, but today
I was focusing more on the correctness.

> [1]

paul moore

  parent reply index

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22  9:33 Jeff Vander Stoep
2019-11-22 14:21 ` Stephen Smalley
2019-12-03  0:32 ` Paul Moore
2019-12-04  9:11   ` Ondrej Mosnacek
2019-12-04 15:48     ` Stephen Smalley
2019-12-04 23:52     ` Paul Moore [this message]
2019-12-05 11:48       ` Ondrej Mosnacek
2019-12-05 14:08         ` Paul Moore
2019-12-05 17:41           ` Paul Moore
2019-12-05 18:10             ` Stephen Smalley
2019-12-05 18:14               ` Paul Moore
2019-12-06  0:50                 ` Paul Moore
2019-12-06 13:45                   ` Stephen Smalley
2019-12-06 15:08                     ` Paul Moore
2019-12-09 21:17   ` Paul Moore

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

SELinux Archive on

Archives are clonable:
	git clone --mirror selinux/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 selinux selinux/ \
	public-inbox-index selinux

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone