From: Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: santosh shilimkar
<santosh.shilimkar-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
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
WARNING: multiple messages have this Message-ID (diff)
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: 6+ 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-05 23:54 ` santosh shilimkar
[not found] ` <54D402BA.2030307-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-02-12 6:09 ` Zefan Li [this message]
2015-02-12 6:09 ` Zefan Li
[not found] ` <54DC439F.2080703-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-02-12 17:30 ` santosh shilimkar
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-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=santosh.shilimkar-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@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 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.