From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.4 released
Date: Tue, 22 May 2012 20:26:04 +0200 [thread overview]
Message-ID: <jpglns$1uj$1@dough.gmane.org> (raw)
In-Reply-To: <20120522170320.GD14339@google.com>
Tejun Heo wrote, on 05/22/12 19:03:
> On Tue, May 22, 2012 at 06:52:49PM +0200, Jörg-Volker Peetz wrote:
>> I tried the above patch but was not able to see a line beginning with "XXX", not
>> on the text-console nor in any log-file. After the hard-lock, I can see only the
>> console-screen which now changed slightly:
>>
>> BUG: Unable to handle kernel NULL pointer dereference at 0000000000000008
>> IP: [<ffffffff8103ed60>] delayed_work_timer_fn+0x30/0x60
>
> Oh, &cwq->wq is at offset 8 so cwq should have been -8. Maybe I'm
> just confused. Can you please try the following instead?
>
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index 5abf42f..14babfe 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -1096,10 +1096,16 @@ queue_work_on(int cpu, struct workqueue_struct *wq, struct work_struct *work)
> }
> EXPORT_SYMBOL_GPL(queue_work_on);
>
> +#include <linux/uaccess.h>
> static void delayed_work_timer_fn(unsigned long __data)
> {
> struct delayed_work *dwork = (struct delayed_work *)__data;
> struct cpu_workqueue_struct *cwq = get_work_cwq(&dwork->work);
> + unsigned long v;
> +
> + if (probe_kernel_read(&v, &cwq->wq, sizeof(v)))
> + printk("XXX delayed_work_timer_fn: cwq %p, fn=%pf\n",
> + cwq, dwork->work.func);
>
> __queue_work(smp_processor_id(), cwq->wq, &dwork->work);
> }
Also with this second patch I wasn't able to see any output beginning with "XXX
delayed_work_timer_fn:". It should appear in the system log or on the text-console?
The screen dump starts with:
BUG: Unable to handle kernel NULL pointer dereference at 0000000000000008
IP: [<ffffffff........>] delayed_work_timer_fn+0x31/0x70
I didn't find the time to type more. Or did I miss the essential?
--
Best regards,
Jörg-Volker.
next prev parent reply other threads:[~2012-05-22 18:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 0:00 Linus Torvalds
2012-05-21 11:38 ` Josh Boyer
2012-05-21 15:20 ` Linus Torvalds
2012-05-21 16:41 ` Josh Boyer
2012-05-21 18:04 ` Tobias Klausmann
2012-05-22 15:30 ` Jörg-Volker Peetz
2012-05-22 15:53 ` Tejun Heo
2012-05-22 16:52 ` Jörg-Volker Peetz
2012-05-22 17:03 ` Tejun Heo
2012-05-22 18:26 ` Jörg-Volker Peetz [this message]
2012-05-22 18:35 ` Tejun Heo
2012-05-22 19:50 ` Jörg-Volker Peetz
2012-05-23 6:34 ` Yong Zhang
2012-05-23 12:33 ` Jörg-Volker Peetz
2012-05-23 18:24 ` Tejun Heo
2012-05-23 19:56 ` Jörg-Volker Peetz
2012-05-23 20:26 ` Tejun Heo
2012-05-25 7:25 ` Takashi Iwai
2012-05-25 15:33 ` Jörg-Volker Peetz
2012-05-25 16:06 ` Takashi Iwai
2012-05-25 18:41 ` Jörg-Volker Peetz
2012-05-27 13:03 ` Jörg-Volker Peetz
2012-05-28 5:16 ` Takashi Iwai
2012-06-06 11:11 ` freeze hard-lock with 3.5-rc1 with dynpm for radeon GPU [was Re: Linux 3.4 released] Jörg-Volker Peetz
2012-08-09 6:47 ` 3.5 kernel NULL pointer dereference net_tx_action Jörg-Volker Peetz
2012-08-10 8:45 ` Jörg-Volker Peetz
2012-05-28 5:16 ` Linux 3.4 released Takashi Iwai
2012-05-25 16:06 ` Takashi Iwai
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='jpglns$1uj$1@dough.gmane.org' \
--to=jvpeetz@web.de \
--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
Powered by JetHome