All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Jarek Poplawski <jarkao2@o2.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	netdev@vger.kernel.org,
	"bugme-daemon\@kernel-bugs\.osdl\.org"
	<bugme-daemon@bugzilla.kernel.org>,
	pterjan@gmail.com
Subject: Re: [PATCH][NET][BRIDGE] br_if: oops in port_carrier_check
Date: Mon, 12 Feb 2007 09:47:38 -0800	[thread overview]
Message-ID: <20070212094738.0a8ae896@localhost.localdomain> (raw)
In-Reply-To: <20070212102848.GA4275@ff.dom.local>

On Mon, 12 Feb 2007 11:28:48 +0100
Jarek Poplawski <jarkao2@o2.pl> wrote:

> Here is my patch proposal for testing.
> If it doesn't work - forget about it.
> (Prepared with 2.6.20-git6 but could
> be applied to 2.6.20 also.)
> 
> Jarek P.
> 
> 
> dev_hold/dev_put added to prevent dev kfree
> during port_carrier_check runnig, while dev
> and port are removed.

No, holding the reference just stops the kfree, it doesn't
stop the device from being removed from the port.

  reply	other threads:[~2007-02-12 17:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 20:52 Fw: [Bugme-new] [Bug 7962] New: oops in port_carrier_check Andrew Morton
2007-02-07 22:09 ` Stephen Hemminger
2007-02-09  7:42   ` Jarek Poplawski
2007-02-09 17:52     ` Stephen Hemminger
2007-02-09 18:50       ` Pascal Terjan
2007-02-12  6:44       ` Jarek Poplawski
2007-02-12 10:28         ` [PATCH][NET][BRIDGE] br_if: " Jarek Poplawski
2007-02-12 17:47           ` Stephen Hemminger [this message]
2007-02-13  6:26             ` Jarek Poplawski
2007-02-13 19:55               ` Stephen Hemminger
2007-02-13 20:35                 ` David Miller
2007-02-14  8:07                   ` Jarek Poplawski

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=20070212094738.0a8ae896@localhost.localdomain \
    --to=shemminger@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=jarkao2@o2.pl \
    --cc=netdev@vger.kernel.org \
    --cc=pterjan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.