From: Zefan Li <lizefan@huawei.com>
To: santosh shilimkar <santosh.shilimkar@oracle.com>
Cc: Tejun Heo <tj@kernel.org>, <cgroups@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG in v3.18 ?] Seems to be triggered from cgroup code
Date: Thu, 12 Feb 2015 14:09:35 +0800 [thread overview]
Message-ID: <54DC439F.2080703@huawei.com> (raw)
In-Reply-To: <54D402BA.2030307@oracle.com>
On 2015/2/6 7:54, santosh shilimkar wrote:
> Hi Tejun and all,
>
> We observed a BUG (stack is end of the email) while trying do some
> ceph testing. I looked at pidlist_free(), pidlist_array_load() for
> any potential leak but those functions looked fine to me.
> The BUG is not 100% reproducible either so though of reporting
> to the list to get some more pointers.
>
By saying not 100% reproducible, do you mean it's reproducible but
not very easy to trigger?
I have to clue how this can happen...This reminds me another bug
report which also happend in pidlist code and it's not reproducible.
https://lkml.org/lkml/2014/9/16/710
next prev parent reply other threads:[~2015-02-12 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 23:54 [BUG in v3.18 ?] Seems to be triggered from cgroup code santosh shilimkar
2015-02-12 6:09 ` Zefan Li [this message]
2015-02-12 17:30 ` santosh shilimkar
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=54DC439F.2080703@huawei.com \
--to=lizefan@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox