public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wouter Verhelst <wouter@grep.be>
To: Pavel Machek <pavel@ucw.cz>
Cc: Paul Clements <paul.clements@steeleye.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nbd: show nbd client pid in sysfs
Date: Mon, 11 Dec 2006 00:18:01 +0100	[thread overview]
Message-ID: <20061210231801.GD29943@country.grep.be> (raw)
In-Reply-To: <20061210195819.GA32577@elf.ucw.cz>

On Sun, Dec 10, 2006 at 08:58:19PM +0100, Pavel Machek wrote:
> Hi!

Hi

> > > > This simple patch allows nbd to expose the nbd-client 
> > > > daemon's PID in /sys/block/nbd<x>/pid. This is helpful 
> > > > for tracking connection status of a device and for 
> > > > determining which nbd devices are currently in use.
> > > 
> > > Actually is it needed at all? Perhaps nbd clients should be modified
> > > to put nbdX in their process nam?
> > 
> > I don't think that's the right approach; only the kernel can guarantee
> > that a given process is actually managing a given nbd device (I could
> > have some rogue process running around announcing that it's managing
> > nbd2, and then what?)
> 
> I'd say "do not run rogue processes as root" :-).
> 
> nbd-client should run as root -- I do not think interface was
> carefully audited to run it as a user -- so rogue process should not
> really be a problem.

IOW, you're suggesting I walk the process list from userspace to find a
process for which a) it claims it's running for a given nbd device, and
b) I can verify that it actually has the permissions to do so. That's a
whole lot of code in comparison to

f=open("/sys/block/nbd2/pid", O_RDONLY);
read(f,buf,len);

I think I very much prefer the above two lines, not only for simplicity.

Also, your suggestion relies on users /only/ using the official
nbd-client, and is fragile in cases where that assumption is false
(i.e., it's susceptible to false negatives). The suggested patch does
not have that problem.

-- 
<Lo-lan-do> Home is where you have to wash the dishes.
  -- #debian-devel, Freenode, 2004-09-22

  reply	other threads:[~2006-12-10 23:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06  2:13 [PATCH] nbd: show nbd client pid in sysfs Paul Clements
2006-12-08 21:16 ` Pavel Machek
2006-12-08 21:17 ` Pavel Machek
2006-12-10 18:07   ` Wouter Verhelst
2006-12-10 19:58     ` Pavel Machek
2006-12-10 23:18       ` Wouter Verhelst [this message]
2006-12-10 23:23         ` Pavel Machek

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=20061210231801.GD29943@country.grep.be \
    --to=wouter@grep.be \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.clements@steeleye.com \
    --cc=pavel@ucw.cz \
    /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