LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: 7eggert@gmx.de
Cc: miklos@szeredi.hu, viro@zeniv.linux.org.uk,
	akpm@linux-foundation.org, linuxram@us.ibm.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/7] vfs: mountinfo (v4)
Date: Thu, 27 Mar 2008 15:42:33 +0100	[thread overview]
Message-ID: <E1JetJJ-0007h2-HQ@pomaz-ex.szeredi.hu> (raw)
In-Reply-To: <E1JesoN-0000ta-Mo@be1.7eggert.dyndns.org> (message from Bodo Eggert on Thu, 27 Mar 2008 15:10:35 +0100)

> > Another update that fixes Al's latest comments:
> > 
> >  - the per-sb options are merged into the fs-specific options
> >  - mount source is shown as a separate field (because commas are not
> >    escaped within it)
> >  - group id checking before allocation/freeing: this one doesn't
> >    actually make a difference for the moment (I hope) but Al's variant
> >    is cleaner
> >  - simplify ID allocation and freeing
> >  - dominator renaming
> >  - function header comment updating
> 
> Is it robust against mounting /dev/$'abc def\x0dghi'
> to ~/mnt/`perl -e 'print "a" x 4050'`?

It is.

> Besides that, I don't like having 'none' as the mount source. Instead, I
> like to e.g. mount proc /proc -t proc, this will put the important
> information into the first column of the mount(1) output, right where I
> start reading.

So do that, this patch doesn't force you to put 'none' in there.

Miklos

  reply	other threads:[~2008-03-27 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <abZpb-4D2-3@gated-at.bofh.it>
2008-03-27 14:10 ` Bodo Eggert
2008-03-27 14:42   ` Miklos Szeredi [this message]
2008-03-27 12:06 Miklos Szeredi

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=E1JetJJ-0007h2-HQ@pomaz-ex.szeredi.hu \
    --to=miklos@szeredi.hu \
    --cc=7eggert@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@us.ibm.com \
    --cc=viro@zeniv.linux.org.uk \
    --subject='Re: [patch 0/7] vfs: mountinfo (v4)' \
    /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

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).