From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
Alexey Dobriyan <adobriyan@gmail.com>,
Pavel Emelyanov <xemul@parallels.com>,
James Bottomley <jbottomley@parallels.com>,
Matthew Helsley <matt.helsley@gmail.com>,
aneesh.kumar@linux.vnet.ibm.com, bfields@fieldses.org,
oleg@redhat.com, rientjes@google.com,
tvrtko.ursulin@onelan.co.uk, Andrey Vagin <avagin@openvz.org>
Subject: Re: [patch 7/7] fs, notify: Add procfs fdinfo helper v6
Date: Mon, 10 Dec 2012 10:47:14 +0400 [thread overview]
Message-ID: <20121210064714.GC1632@moon> (raw)
In-Reply-To: <alpine.LNX.2.01.1212100320180.25777@nerf07.vanv.qr>
On Mon, Dec 10, 2012 at 03:21:53AM +0100, Jan Engelhardt wrote:
>
> On Saturday 2012-11-17 00:56, Andrew Morton wrote:
> >> | pos: 0
> >> | flags: 02000000
> >> | inotify wd: 3 ino: 9e7e
> >> | inotify wd: 2 ino: a111
> >> | inotify wd: 1 ino: 6b149[...]
> >
> >This is a lousy output format. It's sort-of like a sensible set of
> >name-value tuples: "name:value name:value name:value" but
> >
> >c) inotify-wd is secretly printed in decimal while everything else
> > is in hex.
Hi Jan, not secretly, actually, the patch for documentation in -mm tree,
where the format is described.
> >
> >What happens if we do something like the below (which will require a
> >changelog update)?
It's already there :) Andrew pointed to same nit and we've updated
the format. The final one, which sits in -mm is
ret = seq_printf(m, "fhandle-bytes:%x fhandle-type:%x f_handle:",
f.handle.handle_bytes, f.handle.handle_type);
> >
> >@@ -59,7 +59,7 @@ static int show_mark_fhandle(struct seq_
> > f.handle.handle_type = ret;
> > f.handle.handle_bytes = size * sizeof(u32);
> >
> >- ret = seq_printf(m, "fhandle-bytes: %8x fhandle-type: %8x f_handle: ",
> >+ ret = seq_printf(m, "fhandle-bytes:%x fhandle-type:%x f_handle:",
> > f.handle.handle_bytes, f.handle.handle_type);
>
> Why don't we actually make sure to print a 0x prefix when it's hex
> and 0 on octal? Then it should be clear what base these lines are in.
> (That would also be a good idea for the rest of procfs files, but I
> reckon they cannot be easily changed.)
Sounds good for me. If Andrew won't mind I'll update.
Cyrill
next prev parent reply other threads:[~2012-12-10 6:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 15:19 [patch 0/7] Providing additional information in fdinfo sufficient for c/r, v3 Cyrill Gorcunov
2012-11-14 15:19 ` [patch 1/7] procfs: Add ability to plug in auxiliary fdinfo providers Cyrill Gorcunov
2012-11-15 13:47 ` Pavel Emelyanov
2012-11-14 15:19 ` [patch 2/7] fs, eventfd: Add procfs fdinfo helper Cyrill Gorcunov
2012-11-15 13:48 ` Pavel Emelyanov
2012-11-14 15:19 ` [patch 3/7] fs, epoll: Add procfs fdinfo helper v2 Cyrill Gorcunov
2012-11-15 13:49 ` Pavel Emelyanov
2012-11-14 15:19 ` [patch 4/7] fdinfo: Show sigmask for signalfd fd v3 Cyrill Gorcunov
2012-11-15 13:49 ` Pavel Emelyanov
2012-11-14 15:19 ` [patch 5/7] fs, exportfs: Escape nil dereference if no s_export_op present Cyrill Gorcunov
2012-11-15 13:49 ` Pavel Emelyanov
2012-11-14 15:19 ` [patch 6/7] fs, exportfs: Add exportfs_encode_inode_fh helper Cyrill Gorcunov
2012-11-14 17:37 ` J. Bruce Fields
2012-11-15 13:50 ` Pavel Emelyanov
2012-11-14 15:19 ` [patch 7/7] fs, notify: Add procfs fdinfo helper v6 Cyrill Gorcunov
2012-11-15 13:50 ` Pavel Emelyanov
2012-11-16 23:56 ` Andrew Morton
2012-11-17 7:10 ` Cyrill Gorcunov
2012-11-17 8:34 ` Cyrill Gorcunov
2012-11-20 0:49 ` Andrew Morton
2012-11-20 6:35 ` Cyrill Gorcunov
2012-12-10 2:21 ` Jan Engelhardt
2012-12-10 6:47 ` Cyrill Gorcunov [this message]
2012-11-27 0:41 ` Andrew Morton
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=20121210064714.GC1632@moon \
--to=gorcunov@openvz.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=avagin@openvz.org \
--cc=bfields@fieldses.org \
--cc=jbottomley@parallels.com \
--cc=jengelh@inai.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.helsley@gmail.com \
--cc=oleg@redhat.com \
--cc=rientjes@google.com \
--cc=tvrtko.ursulin@onelan.co.uk \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.com \
/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).