From: scream <scream@wdk.dn.ua>
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG] null-pointer in task_rq_lock (2.6.35 to 3.0-rc7)
Date: Mon, 15 Aug 2011 07:22:29 +0000 (UTC) [thread overview]
Message-ID: <loom.20110815T091606-71@post.gmane.org> (raw)
In-Reply-To: 4E25E2F5.7090807@dasr.de
Harald Laabs <kernelml <at> dasr.de> writes:
>
> Hi,
> reloading an apache httpd can crash the kernel since 2.6.35.
> It seems that tasks are removed between creating the task-list and
> calling wake_up_sem_queue_do in freeary. The pointers to the
> task_struct elements end up in try_to_wake_up and sometimes contain
> 0x0 there.
Had the same in production.
Linux version 2.6.35-22-server (buildd@allspice) (gcc version 4.4.5
(Ubuntu/Linaro 4.4.4-14ubuntu4) ) #33-Ubuntu SMP Sun Sep 19 20:48:58 UTC 2010
(Ubuntu 2.6.35-22.33-server 2.6.35.4)
Apache/2.2.16 (Ubuntu) PHP/5.3.3-1ubuntu9 with Suhosin-Patch mod_ssl/2.2.16
OpenSSL/0.9.8o
Appeared 2 times after apache2 reload during cron daily jobs.
prev parent reply other threads:[~2011-08-15 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 20:03 [BUG] null-pointer in task_rq_lock (2.6.35 to 3.0-rc7) Harald Laabs
2011-07-19 21:14 ` Eric Dumazet
2011-07-20 18:11 ` Manfred Spraul
2011-08-15 7:22 ` scream [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=loom.20110815T091606-71@post.gmane.org \
--to=scream@wdk.dn.ua \
--cc=linux-kernel@vger.kernel.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