From: ebiederm@xmission.com (Eric W. Biederman)
To: dilip.daya@hp.com
Cc: netdev@vger.kernel.org
Subject: Re: network-namespace and NETLINK_INET_DIAG - kernel v3.2.39-longterm
Date: Tue, 05 Mar 2013 13:01:43 -0800 [thread overview]
Message-ID: <87boaxd0i0.fsf@xmission.com> (raw)
In-Reply-To: <1362507649.2840.55.camel@pro6455b.example.com> (Dilip Daya's message of "Tue, 05 Mar 2013 13:20:49 -0500")
Dilip Daya <dilip.daya@hp.com> writes:
> Hi Eric et al,
>
> Re: Network-namespace and NETLINK_INET_DIAG
>
> => Network namespace (kernel v3.2.39-longterm) not allowing /bin/ss
> missing information from structs tcp_info and inet_diag_meminfo.
> This is fixed in kernel v3.6-rc1. Are there identifiable patchsets
> from kernel v3.6-rc1 that can be easily backported to
> kernel v3.2.x-longterm ??
Possibly. Certainly the patches that changed this were INET_DIAG
specific. Take a look in the git history.
Not having a feature implemented is not the same as a bug. So I don't
expect anyone is in a rush to backport this.
Eric
prev parent reply other threads:[~2013-03-05 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 18:20 network-namespace and NETLINK_INET_DIAG - kernel v3.2.39-longterm Dilip Daya
2013-03-05 21:01 ` 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=87boaxd0i0.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=dilip.daya@hp.com \
--cc=netdev@vger.kernel.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.