mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: Jiri Slaby <lnx4us@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [2.6.13.3] occasional oops mostly in iget_locked
Date: Fri, 6 Jan 2006 01:31:30 +0100	[thread overview]
Message-ID: <20060106003130.GA21485@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20060105214329.GE10923@vanheusden.com>

Folkert van Heusden <folkert@vanheusden.com> :
[...]
> Well that problem seems to be solved in 2.6.15 so does this problem
> matter anymore? I'm a little hesitant to play a lot with that system as
> it'll make some people really upset.

If you experience random crashes and netconsole is not able to catch
anything, you want to disable netconsole and use a serial console
instead (whenever possible).

I'd say that you do not want netconsole on a non-devel or production
SMP machine.

Side note: even if it does not hit your system, you can probably report
the sequence below to the maintainer of the zaptel module (extracted from
the default branch of current cvs):

static void zt_free_pseudo(struct zt_chan *pseudo)
{
        unsigned long flags;
        if (pseudo) {
                spin_lock_irqsave(&bigzaplock, flags);
                zt_chan_unreg(pseudo);
[...]

static void zt_chan_unreg(struct zt_chan *chan)
{
[...]
                unregister_hdlc_device(chan->hdlcnetdev->netdev);

void unregister_hdlc_device(struct net_device *dev)
{
        rtnl_lock();

-> sleep with spinlock held.

static int zt_ctl_ioctl(struct inode *inode, struct file *file, unsigned int cmd, unsigned long data)
{
[...]
                spin_lock_irqsave(&chans[ch.chan]->lock, flags);
#ifdef CONFIG_ZAPATA_NET
                if (chans[ch.chan]->flags & ZT_FLAG_NETDEV) {
                        if (ztchan_to_dev(chans[ch.chan])->flags & IFF_UP) {
                                spin_unlock_irqrestore(&chans[ch.chan]->lock, flags);
                                printk(KERN_WARNING "Can't switch HDLC net mode on channel %s, since current interface is up\n", chans[ch.chan]->name);
                                return -EBUSY;
                        }
#ifdef LINUX26
[...]
#else
                        unregister_hdlc_device(&chans[ch.chan]->hdlcnetdev->netdev);


-> same thing (btw #ifdef are not fun to review :o| )

--
Ueimor

      reply	other threads:[~2006-01-06  0:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19 19:01 Folkert van Heusden
2005-12-19 19:35 ` Folkert van Heusden
     [not found] ` <3888a5cd0601050849p6ee4cb48s9cc9c9bd6fd20cc8@mail.gmail.com>
2006-01-05 16:51   ` Folkert van Heusden
2006-01-05 21:43   ` Folkert van Heusden
2006-01-06  0:31     ` Francois Romieu [this message]

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=20060106003130.GA21485@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=folkert@vanheusden.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnx4us@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®