From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756873Ab2IDLyL (ORCPT ); Tue, 4 Sep 2012 07:54:11 -0400 Received: from mga01.intel.com ([192.55.52.88]:34437 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756773Ab2IDLyJ (ORCPT ); Tue, 4 Sep 2012 07:54:09 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.80,366,1344236400"; d="scan'208";a="217862194" Date: Tue, 4 Sep 2012 19:54:05 +0800 From: Fengguang Wu To: Jean Delvare Cc: linux-input@vger.kernel.org, Greg Kroah-Hartman , bjorn@mork.no, chunkeey@googlemail.com, linville@tuxdriver.com, LKML , Kay Sievers Subject: Re: input0: bad kobj_uevent_env content in show_uevent() Message-ID: <20120904115405.GA13466@localhost> References: <20120902075946.GA21198@localhost> <20120902083402.GA21787@localhost> <20120904134604.7d95ab2b@endymion.delvare> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20120904134604.7d95ab2b@endymion.delvare> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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:[] [] strnlen+0x23/0x70 > > ... > > [ 32.486234] Call Trace: > > [ 32.486234] [] string.isra.4+0x4c/0x120 > > [ 32.486234] [] vsnprintf+0x2c9/0x900 > > [ 32.486234] [] vscnprintf+0x19/0x50 > > [ 32.486234] [] vprintk_emit+0xe7/0x750 > > [ 32.486234] [] printk+0x4f/0x58 > > [ 32.486234] [] show_uevent+0x1cb/0x220 > > [ 32.486234] [] dev_attr_show+0x2b/0x90 > > [ 32.486234] [] ? sysfs_read_file+0x18a/0x320 > > [ 32.486234] [] ? __get_free_pages+0x24/0xc0 > > [ 32.486234] [] 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