From: Steve Dickson <SteveD@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Artem.Bityutskiy@nokia.com, linux-fsdevel@vger.kernel.org,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/3] Fix handling of explicit uuid
Date: Thu, 28 Aug 2008 11:38:18 -0400 [thread overview]
Message-ID: <48B6C66A.2030705@RedHat.com> (raw)
In-Reply-To: <1219061850.3184.378.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@public.gmane.org>
David Woodhouse wrote:
> Fix a couple of bugs which show up if you try to explicitly set a
> 16-byte UUID when exporting a file system. First, exportfs cuts the
> first two bytes off the UUID and writes something invalid to etab.
> Second, mountd writes the _ascii_ form of the UUID to the kernel,
> instead of converting it to hex.
>
> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Committed...
steved
next prev parent reply other threads:[~2008-08-28 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48A5449F.7050205@nokia.com>
[not found] ` <1218808776.3184.89.camel@pmac.infradead.org>
[not found] ` <1218809892.7037.3.camel@localhost>
[not found] ` <1219058258.3184.358.camel@pmac.infradead.org>
2008-08-18 12:17 ` [PATCH 1/3] Fix handling of explicit uuid David Woodhouse
[not found] ` <1219061850.3184.378.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@public.gmane.org>
2008-08-28 15:38 ` Steve Dickson [this message]
[not found] ` <1219058258.3184.358.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@public.gmane.org>
2008-08-18 12:17 ` [PATCH 2/3] Explicit UUID handling doesn't require blkid; factor out get_uuid_blkdev() David Woodhouse
[not found] ` <1219061859.3184.380.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@public.gmane.org>
2008-08-28 15:38 ` Steve Dickson
2008-08-18 12:17 ` [PATCH 3/3] Use fsid from statfs for UUID if blkid can't cope (or not used) David Woodhouse
[not found] ` <1219061860.3184.382.camel-ZP4jZrcIevRpWr+L1FloEB2eb7JE58TQ@public.gmane.org>
2008-08-28 15:39 ` Steve Dickson
2008-08-18 16:00 ` [PATCH 4/3] Stop exportfs warning about needing fsid, when we actually have one David Woodhouse
2008-08-28 15:39 ` Steve Dickson
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=48B6C66A.2030705@RedHat.com \
--to=steved@redhat.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=dwmw2@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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