From: Petr Tesarik <ptesarik@suse.cz>
To: David Chinner <dgc@sgi.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
lkml <linux-kernel@vger.kernel.org>,
tony.luck@intel.com, linux-ia64@vger.kernel.org
Subject: Re: [ia64] BUG: sleeping in atomic
Date: Fri, 21 Dec 2007 09:15:31 +0100 [thread overview]
Message-ID: <476B7623.3040008@suse.cz> (raw)
In-Reply-To: <20071220043429.GO4612@sgi.com>
David Chinner wrote:
> On Wed, Dec 19, 2007 at 11:42:04AM -0500, Kyle McMartin wrote:
>
>> On Wed, Dec 19, 2007 at 04:54:30PM +1100, David Chinner wrote:
>>
>>> [ 5667.086055] BUG: sleeping function called from invalid context at kernel/fork.c:401
>>>
>>>
>> The problem is that mmput is called under the read_lock by
>> find_thread_for_addr... The comment above seems to indicate that gdb
>> needs to be able to access any child tasks register backing store
>> memory... This seems pretty broken.
>>
>> cheers, Kyle
>>
>> ---
>>
>> Who knows, maybe gdb is saner now?
>>
Well, gdb is saner, but the bug you're talking about will be fixed in a
clean way (even for insane debuggers) with Shaohua's, Roland's and my
fixes to handling the RSE, because they make it possible to get rid of
find_thread_for_addr(). I already sent a mail about it to linux-ia64
some time ago, and Roland suggested we might even change everything to
the generic sys_ptrace(), which is the correct solution (TM), and I'm
planning to do it so as soon as the RSE patches are in.
Regards,
Petr Tesarik
>> diff --git a/arch/ia64/kernel/ptrace.c b/arch/ia64/kernel/ptrace.c
>> index 2e96f17..b609704 100644
>> --- a/arch/ia64/kernel/ptrace.c
>> +++ b/arch/ia64/kernel/ptrace.c
>> @@ -1418,7 +1418,7 @@ asmlinkage long
>> sys_ptrace (long request, pid_t pid, unsigned long addr, unsigned long data)
>> {
>> struct pt_regs *pt;
>> - unsigned long urbs_end, peek_or_poke;
>> + unsigned long urbs_end;
>> struct task_struct *child;
>> struct switch_stack *sw;
>> long ret;
>> @@ -1430,23 +1430,12 @@ sys_ptrace (long request, pid_t pid, unsigned long addr, unsigned long data)
>> goto out;
>> }
>>
>> - peek_or_poke = (request == PTRACE_PEEKTEXT
>> - || request == PTRACE_PEEKDATA
>> - || request == PTRACE_POKETEXT
>> - || request == PTRACE_POKEDATA);
>> - ret = -ESRCH;
>> - read_lock(&tasklist_lock);
>> - {
>> - child = find_task_by_pid(pid);
>> - if (child) {
>> - if (peek_or_poke)
>> - child = find_thread_for_addr(child, addr);
>> - get_task_struct(child);
>> - }
>> - }
>> - read_unlock(&tasklist_lock);
>> - if (!child)
>> + child = ptrace_get_task_struct(pid);
>> + if (IS_ERR(child)) {
>> + ret = PTR_ERR(child);
>> goto out;
>> + }
>> +
>> ret = -EPERM;
>> if (pid == 1) /* no messing around with init! */
>> goto out_tsk;
>>
>
> Yes, this patch fixes the problem (though I haven't tried to
> use gdb yet).
>
> Cheers,
>
> Dave.
>
prev parent reply other threads:[~2007-12-21 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 5:54 [ia64] BUG: sleeping in atomic David Chinner
2007-12-19 16:42 ` Kyle McMartin
2007-12-20 4:34 ` David Chinner
2007-12-21 8:15 ` Petr Tesarik [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=476B7623.3040008@suse.cz \
--to=ptesarik@suse.cz \
--cc=dgc@sgi.com \
--cc=kyle@mcmartin.ca \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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