From: Brandon Low <lostlogic@lostlogicx.com>
To: Tony Mantler <nicoya@ubb.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_MK6 = lsof hangs unkillable
Date: Thu, 16 Feb 2006 19:45:52 -0600 [thread overview]
Message-ID: <20060217014552.GA6861@lostlogicx.com> (raw)
In-Reply-To: <59A5E944-6499-47D4-B875-C0DE75E27701@ubb.ca>
I had this happen earlier today, but at the moment I can't reproduce it.
The offending kernel was 2.6.16-rc3 with CONFIG_MK7=y
I'll post an oops and config if it happens again.
Brandon
On Mon, 01/16/06 at 16:58:55 -0600, Tony Mantler wrote:
>
> On 15-Jan-06, at 10:43 PM, Tony Mantler wrote:
>
> >I'm having trouble running lsof on 2.6.15.1 when the kernel is
> >compiled with CONFIG_MK6. When run as root, lsof will segfault, and
> >when run as a user lsof will hang unkillable.
> >
> >The same kernel, same machine, but compiled with CONFIG_MK7 runs
> >just lsof just fine.
>
> To follow up on this, it appears that things are getting stuck while
> reading /proc/*/maps, specifically it hangs in fs/proc/task_mmu.c in
> m_start() at down_read(&mm->mmap_sem). The same thing happens when
> trying to readlink /proc/*/exe.
>
> I'm really not sure why this lock is getting stuck. Can anyone
> reproduce this?
>
> --
> Tony 'Nicoya' Mantler -- Master of Code-fu -- nicoya@ubb.ca
> -- http://nicoya.feline.pp.se/ -- http://www.ubb.ca/ --
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2006-02-17 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 4:43 CONFIG_MK6 = lsof hangs unkillable Tony Mantler
2006-01-16 22:58 ` Tony Mantler
2006-02-17 1:45 ` Brandon Low [this message]
2006-01-20 12:44 ` Andrew Morton
2006-01-20 20:31 ` Adrian Bunk
2006-01-20 22:41 ` Andrew Morton
2006-01-20 22:47 ` Tony Mantler
2006-01-20 23:39 ` Tony Mantler
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=20060217014552.GA6861@lostlogicx.com \
--to=lostlogic@lostlogicx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicoya@ubb.ca \
/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