From: Jonathan Nieder <jrnieder@gmail.com>
To: Chris Hiestand <chiestand@salk.edu>
Cc: Ben Hutchings <ben@decadent.org.uk>,
669314@bugs.debian.org, viro@zeniv.linux.org.uk,
Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Micheal Waltz <mwaltz@qualcomm.com>,
Gabriel Evanoff <gevanoff@salk.edu>
Subject: Re: NFS: kernel forces trailing slash for export in /proc/self/mounts
Date: Sun, 30 Sep 2012 14:23:41 -0700 [thread overview]
Message-ID: <20120930212341.GA32505@elie.Belkin> (raw)
In-Reply-To: <FB3CAE84-FDFE-4345-9F54-3295BDE2AD81@salk.edu>
Hi Chris,
Chris Hiestand wrote:
> On Sep 16, 2012, at 7:00 AM, Ben Hutchings wrote:
>> This was my first thought - but what if userland provides a device name
>> with a slash on the end? I think we have to report it back with the
>> slash in that case.
[...]
> As a point of comparison, matching the given input is the behavior of 2.6.32-5 in Debian Squeeze.
> So I think your approach is better.
Thanks for looking it over. Did you get a chance to test Ben's patch?
Curious,
Jonathan
next prev parent reply other threads:[~2012-09-30 21:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 19:43 NFS: kernel forces trailing slash for export in /proc/self/mounts Chris Hiestand
2012-09-16 2:21 ` Ben Hutchings
2012-09-16 10:24 ` Chris Hiestand
2012-09-16 14:00 ` Bug#669314: " Ben Hutchings
2012-09-16 20:41 ` Chris Hiestand
2012-09-30 21:23 ` Jonathan Nieder [this message]
2012-10-02 22:37 ` Chris Hiestand
2012-10-18 19:51 ` Chris Hiestand
2012-10-21 18:23 ` [PATCH] nfs: Show original device name verbatim in /proc/*/mount{s,info} Ben Hutchings
2012-10-22 0:01 ` Jonathan Nieder
2012-10-31 17:45 ` Myklebust, Trond
2012-10-31 18:01 ` [PATCH v3] " Jonathan Nieder
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=20120930212341.GA32505@elie.Belkin \
--to=jrnieder@gmail.com \
--cc=669314@bugs.debian.org \
--cc=Trond.Myklebust@netapp.com \
--cc=ben@decadent.org.uk \
--cc=chiestand@salk.edu \
--cc=gevanoff@salk.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mwaltz@qualcomm.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).