From: Ilya Dryomov <idryomov@gmail.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH] Btrfs - use %pU to print fsid
Date: Fri, 1 Apr 2011 01:21:26 +0300 [thread overview]
Message-ID: <20110331222126.GA2630@kwango.lan.net> (raw)
In-Reply-To: <AANLkTik1TAD6EnVKvWZd_ZnzRqyEwkHAJ+s7J5Gm3nsq@mail.gmail.com>
On Thu, Mar 31, 2011 at 12:14:14PM -0500, Mitch Harder wrote:
> On Wed, Feb 9, 2011 at 8:05 AM, Ilya Dryomov <idryomov@gmail.com> wro=
te:
> > Get rid of FIXME comment. =C2=A0Uuids from dmesg are now the same a=
s uuids
> > given by btrfs-progs.
> >
> > Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
> > ---
> > =C2=A0fs/btrfs/volumes.c | =C2=A0 =C2=A08 ++------
> > =C2=A01 files changed, 2 insertions(+), 6 deletions(-)
> >
> > diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> > index 2636a05..83b789c 100644
> > --- a/fs/btrfs/volumes.c
> > +++ b/fs/btrfs/volumes.c
> > @@ -714,12 +714,8 @@ int btrfs_scan_one_device(const char *path, fm=
ode_t flags, void *holder,
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0transid =3D btrfs_super_generation(disk_=
super);
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0if (disk_super->label[0])
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0printk(KERN_=
INFO "device label %s ", disk_super->label);
> > - =C2=A0 =C2=A0 =C2=A0 else {
> > - =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /* FIXME, make a=
readl uuid parser */
> > - =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 printk(KERN_INFO=
"device fsid %llx-%llx ",
> > - =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0*(unsigned long long *)disk_super->fsid,
> > - =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0*(unsigned long long *)(disk_super->fsid + 8));
> > - =C2=A0 =C2=A0 =C2=A0 }
> > + =C2=A0 =C2=A0 =C2=A0 else
> > + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 printk(KERN_INFO=
"device fsid %pU ", disk_super->fsid);
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0printk(KERN_CONT "devid %llu transid %ll=
u %s\n",
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (unsigned long lon=
g)devid, (unsigned long long)transid, path);
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0ret =3D device_list_add(path, disk_super=
, devid, fs_devices_ret);
> > --
> > 1.7.2.3
> >
>=20
> I've had this patch in my testing stack for a while now, and it's bee=
n
> working well. The fsid now matches the UUID.
Chris for some reason didn't add it to the pull request, probably
because it's minor.
> It would be nice if the text string lead off with "Btrfs:" or
> "btrfs:". This would be similar to the way other drivers send log
> messages, and would make it easier to pick out the Btrfs mount messag=
e
> from all the other messages.
Currently there is a mix: some of the messages are printed with
"btrfs:", others with "btrfs", most of the messages informing about
abnormal conditions are printed w/o any prefix. I can resend this one
with "btrfs:" prefix, but I think some kind of decision needed, so this
whole thing can be fixed in one commit.
Thanks,
Ilya
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-31 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 14:05 [PATCH] Btrfs - use %pU to print fsid Ilya Dryomov
2011-03-31 17:14 ` Mitch Harder
2011-03-31 22:21 ` Ilya Dryomov [this message]
2011-06-09 18:02 ` Ilya Dryomov
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=20110331222126.GA2630@kwango.lan.net \
--to=idryomov@gmail.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.