From: Fengguang Wu <fengguang.wu@intel.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-input@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
bjorn@mork.no, chunkeey@googlemail.com, linville@tuxdriver.com,
LKML <linux-kernel@vger.kernel.org>,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: input0: bad kobj_uevent_env content in show_uevent()
Date: Tue, 4 Sep 2012 19:54:05 +0800 [thread overview]
Message-ID: <20120904115405.GA13466@localhost> (raw)
In-Reply-To: <20120904134604.7d95ab2b@endymion.delvare>
On Tue, Sep 04, 2012 at 01:46:04PM +0200, Jean Delvare wrote:
> On Sun, 2 Sep 2012 16:34:02 +0800, Fengguang Wu wrote:
> > It's more than the input device that can trigger the panic.
> > Here is another trace which panics on accessing dmi/id/uevent:
> >
> > [ 32.380795] sysfs_read_file: /sys/devices/virtual/dmi/id/uevent
> > [ 32.399379] dmi id: uevent 73 env[1677721600]: id/.../id
> > [ 32.400780] uevent 0 env[0]: (null)
> > [ 32.401695] uevent 7 env[1]: (null)
> > ...
> > [ 32.478415] general protection fault: 0000 [#1] PREEMPT
> > [ 32.479953] CPU 0
> > [ 32.480433] Pid: 114, comm: trinity-child0 Not tainted 3.6.0-rc4-bisect2-00001-gb6d86d3-dirty #26 Bochs Bochs
> > [ 32.482995] RIP: 0010:[<ffffffff81266c33>] [<ffffffff81266c33>] strnlen+0x23/0x70
> > ...
> > [ 32.486234] Call Trace:
> > [ 32.486234] [<ffffffff81268d5c>] string.isra.4+0x4c/0x120
> > [ 32.486234] [<ffffffff81269f19>] vsnprintf+0x2c9/0x900
> > [ 32.486234] [<ffffffff8126a9c9>] vscnprintf+0x19/0x50
> > [ 32.486234] [<ffffffff8105f8c7>] vprintk_emit+0xe7/0x750
> > [ 32.486234] [<ffffffff81a49ba9>] printk+0x4f/0x58
> > [ 32.486234] [<ffffffff8150522b>] show_uevent+0x1cb/0x220
> > [ 32.486234] [<ffffffff81501dcb>] dev_attr_show+0x2b/0x90
> > [ 32.486234] [<ffffffff81174bea>] ? sysfs_read_file+0x18a/0x320
> > [ 32.486234] [<ffffffff810f2974>] ? __get_free_pages+0x24/0xc0
> > [ 32.486234] [<ffffffff81174c2d>] sysfs_read_file+0x1cd/0x320
>
> I can't reproduce this, sorry, so I can't look into it. If it takes
> special steps to reproduce, please tell me, as I wasn't part of the
> original discussion.
Hi Jean, Bjørn proposed a fix to this bug:
https://lkml.org/lkml/2012/9/2/94
But thank you the same for looking into this!
Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-input@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
bjorn@mork.no, chunkeey@googlemail.com, linville@tuxdriver.com,
LKML <linux-kernel@vger.kernel.org>,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: input0: bad kobj_uevent_env content in show_uevent()
Date: Tue, 4 Sep 2012 19:54:05 +0800 [thread overview]
Message-ID: <20120904115405.GA13466@localhost> (raw)
In-Reply-To: <20120904134604.7d95ab2b@endymion.delvare>
On Tue, Sep 04, 2012 at 01:46:04PM +0200, Jean Delvare wrote:
> On Sun, 2 Sep 2012 16:34:02 +0800, Fengguang Wu wrote:
> > It's more than the input device that can trigger the panic.
> > Here is another trace which panics on accessing dmi/id/uevent:
> >
> > [ 32.380795] sysfs_read_file: /sys/devices/virtual/dmi/id/uevent
> > [ 32.399379] dmi id: uevent 73 env[1677721600]: id/.../id
> > [ 32.400780] uevent 0 env[0]: (null)
> > [ 32.401695] uevent 7 env[1]: (null)
> > ...
> > [ 32.478415] general protection fault: 0000 [#1] PREEMPT
> > [ 32.479953] CPU 0
> > [ 32.480433] Pid: 114, comm: trinity-child0 Not tainted 3.6.0-rc4-bisect2-00001-gb6d86d3-dirty #26 Bochs Bochs
> > [ 32.482995] RIP: 0010:[<ffffffff81266c33>] [<ffffffff81266c33>] strnlen+0x23/0x70
> > ...
> > [ 32.486234] Call Trace:
> > [ 32.486234] [<ffffffff81268d5c>] string.isra.4+0x4c/0x120
> > [ 32.486234] [<ffffffff81269f19>] vsnprintf+0x2c9/0x900
> > [ 32.486234] [<ffffffff8126a9c9>] vscnprintf+0x19/0x50
> > [ 32.486234] [<ffffffff8105f8c7>] vprintk_emit+0xe7/0x750
> > [ 32.486234] [<ffffffff81a49ba9>] printk+0x4f/0x58
> > [ 32.486234] [<ffffffff8150522b>] show_uevent+0x1cb/0x220
> > [ 32.486234] [<ffffffff81501dcb>] dev_attr_show+0x2b/0x90
> > [ 32.486234] [<ffffffff81174bea>] ? sysfs_read_file+0x18a/0x320
> > [ 32.486234] [<ffffffff810f2974>] ? __get_free_pages+0x24/0xc0
> > [ 32.486234] [<ffffffff81174c2d>] sysfs_read_file+0x1cd/0x320
>
> I can't reproduce this, sorry, so I can't look into it. If it takes
> special steps to reproduce, please tell me, as I wasn't part of the
> original discussion.
Hi Jean, Bjørn proposed a fix to this bug:
https://lkml.org/lkml/2012/9/2/94
But thank you the same for looking into this!
Thanks,
Fengguang
next prev parent reply other threads:[~2012-09-04 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 7:59 input0: bad kobj_uevent_env content in show_uevent() Fengguang Wu
2012-09-02 8:34 ` Fengguang Wu
2012-09-02 8:37 ` Fengguang Wu
2012-09-04 11:46 ` Jean Delvare
2012-09-04 11:54 ` Fengguang Wu [this message]
2012-09-04 11:54 ` Fengguang Wu
2012-09-04 11:56 ` Bjørn Mork
2012-09-02 13:41 ` Bjørn Mork
2012-09-02 13:41 ` Bjørn Mork
2012-09-02 16:38 ` Fengguang Wu
2012-09-02 16:38 ` Fengguang Wu
2012-09-03 0:22 ` Greg Kroah-Hartman
2012-09-03 7:01 ` Bjørn Mork
2012-09-03 7:01 ` Bjørn Mork
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=20120904115405.GA13466@localhost \
--to=fengguang.wu@intel.com \
--cc=bjorn@mork.no \
--cc=chunkeey@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kay.sievers@vrfy.org \
--cc=khali@linux-fr.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.