From: Tejun Heo <tj@kernel.org>
To: Wang Xiaoming <xiaoming.wang@intel.com>
Cc: akpm@linux-foundation.org, oleg@redhat.com,
andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk,
ebiederm@xmission.com, eparis@redhat.com,
chenhanxiao@cn.fujitsu.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, "Schallberger,
Timothy M" <timothy.m.schallberger@intel.com>,
Dongxing Zhang <dongxing.zhang@intel.com>
Subject: Re: [PATCH] proc: move the adding option Ngid to the end of proc/PID/status
Date: Thu, 16 Apr 2015 22:56:24 -0400 [thread overview]
Message-ID: <20150417025624.GA12709@htj.duckdns.org> (raw)
In-Reply-To: <1429236796-22387-1-git-send-email-xiaoming.wang@intel.com>
On Fri, Apr 17, 2015 at 10:13:15AM +0800, Wang Xiaoming wrote:
> Move debugging has been done and the following Kernel issue
> was found with a number of applications.
> Take a look at: (even though the comments are for Weibo.browser
> they also pertain to other apps that use Libsecuritysdk-x.x.x.so
>
> In kernel(3.14) is a little different than before
> it will generate /proc/PID/status in this way:
> Name: a.weibo.browser
> State: T (stopped)
> Tgid: 8487
> Ngid: 0 ---- add in kernel after (3.11 maybe)
Well, that's kinda hilarious and I don't know. 3.11 is way back and
what if there are others depending on the current ordering? Both
situations kinda suck so what's the point of changing?
--
tejun
next prev parent reply other threads:[~2015-04-17 2:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 2:13 [PATCH] proc: move the adding option Ngid to the end of proc/PID/status Wang Xiaoming
2015-04-17 2:56 ` Tejun Heo [this message]
2015-04-17 3:15 ` Wang, Xiaoming
2015-04-17 3:26 ` Tejun Heo
2015-04-17 3:37 ` Wang, Xiaoming
2015-04-17 3:42 ` Tejun Heo
2015-04-17 5:36 ` Wang, Xiaoming
2015-04-21 15:19 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2015-04-17 13:23 Alexey Dobriyan
2015-04-17 14:26 ` Tejun Heo
2015-04-17 15:05 ` Alexey Dobriyan
2015-04-17 15:12 ` Tejun Heo
2015-04-21 8:19 ` Wang, Xiaoming
2015-04-21 14:00 ` Alexey Dobriyan
2015-04-21 15:11 ` Tejun Heo
2015-04-23 20:32 ` Alexey Dobriyan
2015-04-24 15:50 ` Tejun Heo
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=20150417025624.GA12709@htj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chenhanxiao@cn.fujitsu.com \
--cc=dongxing.zhang@intel.com \
--cc=ebiederm@xmission.com \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
--cc=timothy.m.schallberger@intel.com \
--cc=xiaoming.wang@intel.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