mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org,
	containers@lists.linux-foundation.org, serge.hallyn@ubuntu.com,
	eparis@redhat.com, sgrubb@redhat.com, ebiederm@xmission.com
Subject: Re: [PATCH 1/2] namespaces: give each namespace a serial number
Date: Fri, 2 May 2014 00:51:16 +0200	[thread overview]
Message-ID: <20140501225116.GB25669@mail.hallyn.com> (raw)
In-Reply-To: <be1358c6da51252cd79c51a51bb30bf157624ccd.1398176489.git.rgb@redhat.com>

Quoting Richard Guy Briggs (rgb@redhat.com):

Most of this looks reasonable, but I'm curious about something,

> +/**
> + * ns_serial - compute a serial number for the namespace
> + *
> + * Compute a serial number for the namespace to uniquely identify it in
> + * audit records.
> + */
> +unsigned int ns_serial(void)
> +{
> +	static DEFINE_SPINLOCK(serial_lock);
> +	static unsigned int serial = 4; /* reserved for IPC, UTS, user, PID */
> +
> +	unsigned long flags;
> +	unsigned int ret;
> +
> +	spin_lock_irqsave(&serial_lock, flags);
> +	do {
> +		ret = ++serial;
> +	} while (unlikely(!ret));

Why exactly are you doing this?  Surely if serial is going to
wrap around we've got a bigger problem than just wanting go
bump one more time?

> +	spin_unlock_irqrestore(&serial_lock, flags);
> +
> +	return ret;
> +}

  reply	other threads:[~2014-05-01 22:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 18:12 [PATCH 0/2] namespaces: log namespaces per task Richard Guy Briggs
2014-04-22 18:12 ` [PATCH 1/2] namespaces: give each namespace a serial number Richard Guy Briggs
2014-05-01 22:51   ` Serge E. Hallyn [this message]
2014-05-02 14:15     ` Richard Guy Briggs
2014-05-02 20:50       ` Serge Hallyn
2014-04-22 18:12 ` [PATCH 2/2] audit: log namespace serial numbers Richard Guy Briggs
2014-05-01 23:01   ` Serge E. Hallyn
2014-05-01 22:32 ` [PATCH 0/2] namespaces: log namespaces per task Serge E. Hallyn
2014-05-02 14:28   ` Richard Guy Briggs
2014-05-02 21:00     ` Serge Hallyn
2014-05-05 21:29       ` Richard Guy Briggs
2014-05-05  9:23     ` Nicolas Dichtel
2014-05-06 21:15       ` Richard Guy Briggs
2014-05-07  9:35         ` Nicolas Dichtel
2014-05-03 21:58 ` James Bottomley
2014-05-05  3:48   ` Serge E. Hallyn
2014-05-05 21:48     ` Richard Guy Briggs
2014-05-05 21:51       ` James Bottomley
2014-05-05 22:11         ` Richard Guy Briggs
2014-05-05 22:24           ` James Bottomley
2014-05-05 22:27         ` Serge Hallyn
2014-05-05 22:30           ` James Bottomley
2014-05-05 22:36             ` Serge Hallyn
2014-05-05 23:23               ` James Bottomley
2014-05-06  3:27                 ` Serge Hallyn
2014-05-06  4:59                   ` James Bottomley
2014-05-06 14:50                     ` Serge Hallyn
2014-05-06 21:59                     ` Richard Guy Briggs
2014-05-06 12:35                 ` Nicolas Dichtel
2014-05-06 21:41                 ` Richard Guy Briggs
2014-05-06 23:57                   ` James Bottomley
2014-05-05 21:44   ` Richard Guy Briggs
2014-05-06  3:33     ` Serge Hallyn
2014-05-06 14:03       ` Richard Guy Briggs

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=20140501225116.GB25669@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=eparis@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgb@redhat.com \
    --cc=serge.hallyn@ubuntu.com \
    --cc=sgrubb@redhat.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

all inboxes | Powered by JetHome®