From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Alban Crequy <alban.crequy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Iago Lopez Galeiras
<iago-lYLaGTFnO9sWenYVfaLwtA@public.gmane.org>,
Aaron Campbell <aaron-J6AcJDG0ZEwdnm+yROfE0A@public.gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Jiri Benc <jbenc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Jesper Derehag <jderehag-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>,
Alban Crequy <alban-lYLaGTFnO9sWenYVfaLwtA@public.gmane.org>,
Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Evgeniy Polyakov <zbr-i6C2adt8DTjR7s880joybQ@public.gmane.org>,
Dimitri John Ledkov
<dimitri.j.ledkov-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [RFC v2 0/2] proc connector: get namespace events
Date: Sun, 16 Oct 2016 09:57:32 -0500 [thread overview]
Message-ID: <87twcctk83.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <1476534370-4027-1-git-send-email-alban-lYLaGTFnO9sWenYVfaLwtA@public.gmane.org> (Alban Crequy's message of "Sat, 15 Oct 2016 14:26:08 +0200")
Alban Crequy <alban.crequy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> This is v2 of the patch set to add namespace events in the proc
> connector.
So while not totally wrong the way you report namespaces makes me
grumpy. You are not including the device node of the filesystem
those inodes are on. The inode number is meaningless if you don't
specify which filesystem the inode is from.
I absolutely do not want to have to implement a namespace for namespaces
someday just because people have been sloppy like this.
So please correct this to at least report the full information on
namespaces.
Thank you,
Eric
prev parent reply other threads:[~2016-10-16 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 12:26 [RFC v2 0/2] proc connector: get namespace events Alban Crequy
[not found] ` <1476534370-4027-1-git-send-email-alban-lYLaGTFnO9sWenYVfaLwtA@public.gmane.org>
2016-10-15 12:26 ` [RFC v2 1/2] proc connector: add " Alban Crequy
[not found] ` <1476534370-4027-2-git-send-email-alban-lYLaGTFnO9sWenYVfaLwtA@public.gmane.org>
2016-10-20 17:12 ` Evgeniy Polyakov
2016-10-15 12:26 ` [RFC v2 2/2] proc connector: add a "get feature" op Alban Crequy
[not found] ` <1476534370-4027-3-git-send-email-alban-lYLaGTFnO9sWenYVfaLwtA@public.gmane.org>
2016-10-20 17:16 ` Evgeniy Polyakov
2016-10-16 14:57 ` Eric W. Biederman [this message]
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=87twcctk83.fsf@x220.int.ebiederm.org \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=aaron-J6AcJDG0ZEwdnm+yROfE0A@public.gmane.org \
--cc=alban-lYLaGTFnO9sWenYVfaLwtA@public.gmane.org \
--cc=alban.crequy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=dimitri.j.ledkov-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=iago-lYLaGTFnO9sWenYVfaLwtA@public.gmane.org \
--cc=jbenc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jderehag-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=zbr-i6C2adt8DTjR7s880joybQ@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