public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Fulghum <paulkf@microgate.com>
To: Bob Copeland <email@bobcopeland.com>
Cc: paulus@samba.org, Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.16-rc5 pppd oops on disconnects
Date: Fri, 10 Mar 2006 13:25:09 -0600	[thread overview]
Message-ID: <1142018709.26063.5.camel@amdx2.microgate.com> (raw)
In-Reply-To: <b6c5339f0603101048l1c362582xc4d2570bc9d569b@mail.gmail.com>

On Fri, 2006-03-10 at 13:48 -0500, Bob Copeland wrote:
> > > Call Trace:
> > >  [<c017592e>] sysfs_hash_and_remove+0x34/0x10a
> > >  [<c01e756e>] class_device_del+0xa0/0x11c
> > >  [<c01e75f5>] class_device_unregister+0xb/0x16
> > >  [<d01f81f3>] acm_tty_unregister+0x1d/0x63 [cdc_acm]
> >
> > This looks more like
> > http://bugzilla.kernel.org/show_bug.cgi?id=5876
> 
> Hmm... it looks different from that bug - in that case the root cause
> was sysfs_make_dirent failing, presumably when the sysfs node for the
> device was being set up, by unplugging and re-plugging the device a
> lot.  Here it's oopsing when the node is being removed, after it's
> been in use a while and unplugged only once.  But yes ppp may not have
> anything to do with it.  I'll try it on an older kernel to see if I
> can reproduce there...

The i_sem to i_mutex change started in the 2.6.16 series.
Running against 2.6.15 would be interesting. Being able
to repeat every time is a plus. I'm not that familiar
with the sysfs stuff, but the slab poisoning is pretty
damning. The dentry was released and then accessed.

I looked at cdc_acm for disconnect and close and
did not see any problems (such as trying to call
tty_unregister_device twice for a device).

-- 
Paul Fulghum
Microgate Systems, Ltd


  reply	other threads:[~2006-03-10 19:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10 14:25 2.6.16-rc5 pppd oops on disconnects Bob Copeland
2006-03-10 17:22 ` Paul Fulghum
2006-03-10 18:48   ` Bob Copeland
2006-03-10 19:25     ` Paul Fulghum [this message]
2006-03-11 15:09       ` Bob Copeland
2006-03-11 17:56         ` Paul Fulghum
2006-03-11 20:21           ` Bob Copeland
2006-03-11 21:57             ` Paul Fulghum
2006-03-12 16:26             ` Paul Fulghum
2006-03-12 17:58               ` Bob Copeland
2006-03-12 20:09                 ` [linux-usb-devel] " Oliver Neukum
2006-03-12 21:30                   ` Bob Copeland
2006-03-13  2:21                 ` Paul Fulghum
2006-03-12  5:35 ` Greg KH
2006-03-12 16:31   ` Bob Copeland

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=1142018709.26063.5.camel@amdx2.microgate.com \
    --to=paulkf@microgate.com \
    --cc=email@bobcopeland.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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