public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: kernel BUG with 2.6.23-rc3-mm1: skb_over_panic
Date: Fri, 24 Aug 2007 17:46:40 -0700	[thread overview]
Message-ID: <20070825004640.GA21756@kroah.com> (raw)
In-Reply-To: <20070824174450.70337f4f.akpm@linux-foundation.org>

On Fri, Aug 24, 2007 at 05:44:50PM -0700, Andrew Morton wrote:
> On Fri, 24 Aug 2007 20:16:38 -0400
> Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> 
> > * Andrew Morton (akpm@linux-foundation.org) wrote:
> > > On Fri, 24 Aug 2007 18:47:07 -0400
> > > Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> > > 
> > > > Hi Andrew,
> > > > 
> > > > I get the following BUG when booting 2.6.23-rc3-mm1 on i386. I wonder if
> > > > you would have some ideas about what is causing this problem. I'll start
> > > > bissecting it soon. I seems to be caused by an buggy skb_put call in
> > > > kobject_uevent_env.
> > > > 
> > > > Thanks,
> > > > 
> > > > Mathieu
> > > > 
> > > > 
> > > 
> > > hm, don't know, sorry.  Kay fixed a few things in there, but iirc pretty
> > > much all of the fixes were in rc3-mm1 anyway.
> > > 
> > > I doubt if bisection will tell us a lot: it'll probably point at
> > > gregkh-driver-driver-core-change-add_uevent_var-to-use-a-struct.patch.
> > > 
> > > What we _would_ like to know is which sysfs file is being written to.  We
> > > used to have a debug patch to exactly address this problem but it got
> > > transferred into Greg's tree from whence it mysteriously disappeared.
> > > 
> > 
> > Ok, here it is:
> > 
> > filename :
> > 
> > /devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/rev
> 
> Bah.  I've never found a sane way of going from a sysfs pathname back to the
> code which implements that pathname :(
> 
> <greps the tree for '"rev"'>
> 
> <comes up with zilch>

It's a scsi file, as the above is a scsi device.  It's created in the
drivers/scsi/scsi_sysfs.c file.

Kay, did you miss this set of attributes somehow?

thanks,

greg k-h

  reply	other threads:[~2007-08-25  0:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 22:47 kernel BUG with 2.6.23-rc3-mm1: skb_over_panic Mathieu Desnoyers
2007-08-24 23:10 ` Andrew Morton
2007-08-24 23:46   ` Greg KH
2007-08-25  0:16   ` Mathieu Desnoyers
2007-08-25  0:44     ` Andrew Morton
2007-08-25  0:46       ` Greg KH [this message]
2007-08-25  1:26         ` Kay Sievers
2007-08-25  3:02         ` Mathieu Desnoyers
2007-08-25  3:44           ` Kay Sievers
2007-08-25  3:52             ` Mathieu Desnoyers
2007-08-25  3:56             ` Mathieu Desnoyers
2007-08-25  3:58             ` Daniel Walker
2007-08-25  4:17         ` [PATCH] Fix kobject uevent string handling errors Mathieu Desnoyers
2007-08-25  4:49           ` Greg KH
2007-08-25 14:25           ` Kay Sievers
2007-08-25 18:38             ` Mathieu Desnoyers
2007-08-25  1:59       ` kernel BUG with 2.6.23-rc3-mm1: skb_over_panic Randy Dunlap

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=20070825004640.GA21756@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    /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