From: David Miller <davem@davemloft.net>
To: mattilinnanvuori@yahoo.com
Cc: jgarzik@pobox.com, netdev@vger.kernel.org,
bugme-daemon@kernel-bugs.osdl.org
Subject: Re: [Bug 9750] [patch 2.6.25] dev: avoid a race that triggers assertion failure
Date: Tue, 12 Feb 2008 18:16:16 -0800 (PST) [thread overview]
Message-ID: <20080212.181616.181583250.davem@davemloft.net> (raw)
In-Reply-To: <190693.34289.qm@web52005.mail.re2.yahoo.com>
From: Matti Linnanvuori <mattilinnanvuori@yahoo.com>
Date: Tue, 12 Feb 2008 02:45:22 -0800 (PST)
> From: Matti Linnanvuori <mattilinnanvuori@yahoo.com>
>
> There is a race in Linux kernel file net/core/dev.c, function dev_close.
> The function calls function dev_deactivate, which calls function
> dev_watchdog_down that deletes the watchdog timer. However, after that, a
> driver can call netif_carrier_ok, which calls function
> __netdev_watchdog_up that can add the watchdog timer again. Function
> unregister_netdevice calls function dev_shutdown that traps the bug
> !timer_pending(&dev->watchdog_timer). Moving dev_deactivate after
> netif_running() has been cleared prevents function netif_carrier_on
> from calling __netdev_watchdog_up and adding the watchdog timer again.
>
> Signed-off-by: Matti Linnanvuori <mattilinnanvuori@yahoo.com>
Your patch won't apply because it has been whitespace damanged
by your email client.
This is what I let you know last time you posted this patch.
Please fix this up so that your patch can be applied.
Thanks.
prev parent reply other threads:[~2008-02-13 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 10:45 [Bug 9750] [patch 2.6.25] dev: avoid a race that triggers assertion failure Matti Linnanvuori
2008-02-12 15:58 ` Jeff Garzik
2008-02-13 2:16 ` David Miller [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=20080212.181616.181583250.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bugme-daemon@kernel-bugs.osdl.org \
--cc=jgarzik@pobox.com \
--cc=mattilinnanvuori@yahoo.com \
--cc=netdev@vger.kernel.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