From: Fengguang Wu <fengguang.wu@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Kay Sievers <kay.sievers@vrfy.org>,
devel@driverdev.osuosl.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: show_uevent() and general protection fault
Date: Wed, 18 Jul 2012 13:15:52 +0800 [thread overview]
Message-ID: <20120718051552.GA9124@localhost> (raw)
In-Reply-To: <20120717013342.GD21914@kroah.com>
On Mon, Jul 16, 2012 at 06:33:42PM -0700, Greg Kroah-Hartman wrote:
> On Fri, Jul 13, 2012 at 04:46:16PM +0800, Fengguang Wu wrote:
> > This is another kconfig, produced a bit different call trace, however
> > also related to sysfs_read_file().
>
> Any hint as to which file is being read?
Good idea! I added this debugging aid:
--- a/fs/sysfs/file.c
+++ b/fs/sysfs/file.c
@@ -129,6 +129,11 @@ sysfs_read_file(struct file *file, char __user *buf, size_t count, loff_t *ppos)
{
struct sysfs_buffer * buffer = file->private_data;
ssize_t retval = 0;
+ char pathname[300], *path;
+
+ path = d_path(&(file->f_path), pathname, sizeof(pathname));
+ if (!IS_ERR(path))
+ printk("%s\n", path);
mutex_lock(&buffer->mutex);
if (buffer->needs_read_fill || *ppos == 0) {
And find some sysfs files that triggered the errors:
wfg@waimea ~/kvm% grep -hB1 'kernel paging request' /tmp/dmesg-kvm_bisect-waimea-*|grep /sys/
[ 28.995741] /sys/module/tpm_tis/parameters/hid
[ 60.885798] /sys/module/tpm_tis/parameters/hid
wfg@waimea ~/kvm% grep -hB1 'general protection fault' /tmp/dmesg-kvm_bisect-waimea-*|grep -o /sys/.* | sort -u
/sys/devices/LNXSYSTM:00/device:00/PNP0103:00/uevent
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:21/PNP0303:00/uevent
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:21/PNP0400:00/uevent
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:21/PNP0501:00/uevent
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:21/PNP0700:00/uevent
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:21/PNP0B00:00/uevent
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:21/PNP0F13:00/uevent
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/uevent
/sys/devices/LNXSYSTM:00/device:00/PNP0C0F:00/uevent
/sys/devices/LNXSYSTM:00/device:00/PNP0C0F:01/uevent
/sys/devices/LNXSYSTM:00/device:00/PNP0C0F:02/uevent
/sys/devices/LNXSYSTM:00/device:00/PNP0C0F:03/uevent
/sys/devices/LNXSYSTM:00/LNXCPU:00/uevent
/sys/devices/LNXSYSTM:00/LNXCPU:01/uevent
/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0/uevent
/sys/devices/LNXSYSTM:00/LNXPWRBN:00/uevent
/sys/devices/LNXSYSTM:00/uevent
/sys/devices/platform/i8042/serio0/input/input1/uevent
Thanks,
Fengguang
next prev parent reply other threads:[~2012-07-18 5:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 7:59 show_uevent() and general protection fault Fengguang Wu
2012-07-13 8:31 ` Fengguang Wu
2012-07-13 8:46 ` Fengguang Wu
2012-07-17 1:33 ` Greg Kroah-Hartman
2012-07-18 5:15 ` Fengguang Wu [this message]
2012-08-16 17:27 ` Greg Kroah-Hartman
2012-08-17 2:06 ` Fengguang Wu
2012-08-17 2:29 ` Fengguang Wu
2012-08-17 2:44 ` Ming Lei
2012-08-17 2:56 ` Fengguang Wu
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=20120718051552.GA9124@localhost \
--to=fengguang.wu@intel.com \
--cc=cornelia.huck@de.ibm.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).