cgroups.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: santosh shilimkar <santosh.shilimkar-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Zefan Li <lizefan-hv44wF8Li93QT0dZR+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 09:30:54 -0800	[thread overview]
Message-ID: <54DCE34E.1010307@oracle.com> (raw)
In-Reply-To: <54DC439F.2080703-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>



On 2/11/2015 10:09 PM, Zefan Li wrote:
> 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?
>
Right. We saw it only once in 20+ attempts.

> 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
>
I was just trying my luck if I can get some more ideas about the
potential cause.

Thanks for the response !!

Regards,
Santosh

      parent reply	other threads:[~2015-02-12 17:30 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
     [not found] ` <54D402BA.2030307-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-02-12  6:09   ` Zefan Li
     [not found]     ` <54DC439F.2080703-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-02-12 17:30       ` santosh shilimkar [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=54DCE34E.1010307@oracle.com \
    --to=santosh.shilimkar-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lizefan-hv44wF8Li93QT0dZR+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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).