From: "Robert Święcki" <robert@swiecki.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Oleg Nesterov" <oleg@redhat.com>,
"Américo Wang" <xiyou.wangcong@gmail.com>,
linux-kernel@vger.kernel.org, "Hugh Dickins" <hughd@google.com>,
"Miklos Szeredi" <mszeredi@suse.cz>
Subject: Re: Processes hang in an unkillable state
Date: Tue, 12 Apr 2011 23:59:37 +0200 [thread overview]
Message-ID: <BANLkTinjGkbBMUo7MQ2Dg2yDwQ932qJ7rQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinMAGmdEDviRwZ1-mxrAAe_WK5jvg@mail.gmail.com>
>> Ok, just to update you with what I'm currently doing:
>>
>> I'm testing now with 2.6.39-rc3 - according to
>> http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.39-rc3
>> it has vma_to_resize patch included
>> (982134ba62618c2d69fbbbd166d0a11ee3b7e3d8) - I applied the latest
>> Linus' patch for sys_mlock (the one patching memory.c and mlock.c),
>> disabled the sys_madvise in the fuzzer, and now I got the following
>> (full kdb dump attached)
>
> Ok, that's different from the apparent livelock.
>
> Except it once again is one of the BUG_ON's in vma_prio_tree_add() -
> and again, your kgdb thing has corrupted the bug information.
>
> Can you make a bug-report to the kgdb people?
Ok,
> You've lost Hugh's patch that did the vma dump instead of having the
> BUG_ON(). Can you try that one? And once more, I think that if you had
> CONFIG_OPTIMIZE_SIZE on, then I think gcc wouldn't re-order the basic
> blocks, and the BUG_ON() info would be easier to track.
Compiling now with CONFIG_OPTIMIZE_SIZE and vma dump code. Will
probably post some results tomorrow.
--
Robert Święcki
next prev parent reply other threads:[~2011-04-12 21:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 10:32 Robert Święcki
2011-04-12 12:44 ` Américo Wang
2011-04-12 13:03 ` Robert Święcki
2011-04-12 13:08 ` Robert Święcki
2011-04-12 18:28 ` Oleg Nesterov
2011-04-12 18:34 ` Robert Święcki
2011-04-12 19:20 ` Oleg Nesterov
[not found] ` <BANLkTimJgx_x=0bpBDWaUkJgZPYs3_iwsg@mail.gmail.com>
[not found] ` <BANLkTimBegMUq2fX67o2YnoATWG-NDbKgA@mail.gmail.com>
2011-04-12 20:22 ` Linus Torvalds
[not found] ` <BANLkTi=HyK+8DhJS3db0j2fefdOjwVMN3w@mail.gmail.com>
2011-04-12 21:46 ` Linus Torvalds
2011-04-12 21:59 ` Robert Święcki [this message]
2011-04-12 22:12 ` Linus Torvalds
2011-04-12 22:16 ` Robert Święcki
2011-04-12 22:18 ` Linus Torvalds
2011-04-12 22:30 ` Robert Święcki
2011-04-12 22:43 ` Linus Torvalds
2011-04-13 12:19 ` Robert Święcki
2011-04-12 19:07 ` [PATCH 0/1] Was: " Oleg Nesterov
2011-04-12 19:08 ` [PATCH 1/1] __mlock_vma_pages_range: stack_guard_page() case returns the wrong value Oleg Nesterov
2011-04-12 19:18 ` Robert Święcki
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=BANLkTinjGkbBMUo7MQ2Dg2yDwQ932qJ7rQ@mail.gmail.com \
--to=robert@swiecki.net \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.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
all inboxes | Powered by JetHome®