Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759182AbYC0Om6 (ORCPT ); Thu, 27 Mar 2008 10:42:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756472AbYC0Omt (ORCPT ); Thu, 27 Mar 2008 10:42:49 -0400 Received: from fxip-0047f.externet.hu ([88.209.222.127]:36964 "EHLO pomaz-ex.szeredi.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753241AbYC0Oms (ORCPT ); Thu, 27 Mar 2008 10:42:48 -0400 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 In-reply-to: (message from Bodo Eggert on Thu, 27 Mar 2008 15:10:35 +0100) Subject: Re: [patch 0/7] vfs: mountinfo (v4) References: Message-Id: From: Miklos Szeredi Date: Thu, 27 Mar 2008 15:42:33 +0100 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1154 Lines: 30 > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/