From: Jonathan Nieder <jrnieder-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Chris Hiestand <chiestand-xrR1t/MlNfQ@public.gmane.org>
Cc: Ben Hutchings <ben-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>,
669314-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org,
viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org,
Trond Myklebust
<Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Micheal Waltz <mwaltz-zC7DfRvBq/JWk0Htik3J/w@public.gmane.org>,
Gabriel Evanoff <gevanoff-xrR1t/MlNfQ@public.gmane.org>
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-xrR1t/MlNfQ@public.gmane.org>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
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 Bug#669314: 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 ` Bug#669314: " Chris Hiestand
[not found] ` <254E1AAA-BDE2-41A8-94D8-6E677860AD72-xrR1t/MlNfQ@public.gmane.org>
2012-09-16 14:00 ` Ben Hutchings
[not found] ` <1347804028.13258.267.camel-nDn/Rdv9kqW9Jme8/bJn5UCKIB8iOfG2tUK59QYPAWc@public.gmane.org>
2012-09-16 20:41 ` Chris Hiestand
[not found] ` <FB3CAE84-FDFE-4345-9F54-3295BDE2AD81-xrR1t/MlNfQ@public.gmane.org>
2012-09-30 21:23 ` Jonathan Nieder [this message]
[not found] ` <20120930212341.GA32505-fcEM2ccDkbL2nhBuCrrZHw@public.gmane.org>
2012-10-02 22:37 ` Chris Hiestand
[not found] ` <B259EBD8-0ED1-405F-A3E5-DF488FCE402F-xrR1t/MlNfQ@public.gmane.org>
2012-10-18 19:51 ` Chris Hiestand
[not found] ` <7941E5E1-488D-4D0B-A21A-4E389EF6EBBA-xrR1t/MlNfQ@public.gmane.org>
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
[not found] ` <4FA345DA4F4AE44899BD2B03EEEC2FA90929FA9E-VGJ86jkg8PeBTCzCEi1xmXOR4cbS7gtM96Bgd4bDwmQ@public.gmane.org>
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-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=669314-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org \
--cc=Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
--cc=ben-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org \
--cc=chiestand-xrR1t/MlNfQ@public.gmane.org \
--cc=gevanoff-xrR1t/MlNfQ@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mwaltz-zC7DfRvBq/JWk0Htik3J/w@public.gmane.org \
--cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org \
/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).