From: Andrew Morton <andrewm@uow.edu.au>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Philipp Rumpf <prumpf@parcelfarce.linux.theplanet.co.uk>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PROPOSED PATCH] ATM refcount + firestream
Date: Sun, 29 Oct 2000 03:10:16 +1100 [thread overview]
Message-ID: <39FAFA68.A8250BA@uow.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.21.0010270945510.13233-200000@panoramix.bitwizard.nl> <39F96BE1.B9C97C20@uow.edu.au> <20001028141518.A2272@parcelfarce.linux.theplanet.co.uk> <39FAD698.2FF9C8C8@didntduck.org> <20001028145312.B2272@parcelfarce.linux.theplanet.co.uk> <39FADAC9.DC1255D1@didntduck.org> <20001028160537.C2272@parcelfarce.linux.theplanet.co.uk> <39FAF5BE.C79801A2@didntduck.org>
Brian Gerst wrote:
>
> With or without your patch, the network ioctls are unsafe, since they
> don't currently do refcounting at all. Adding it in the layer above the
> driver is the easier and cleaner solution.
As long as the drivers use unregister_netdevice() then that's
fairly easy to fix within the netdevice layer. Just do a
dev_hold()/dev_put() within dev_ifsioc().
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-28 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 7:50 [PROPOSED PATCH] ATM refcount + firestream Patrick van de Lageweg
2000-10-27 11:49 ` Andrew Morton
2000-10-27 13:49 ` Brian Gerst
2000-10-27 14:34 ` Patrick van de Lageweg
2000-10-27 14:49 ` Brian Gerst
2000-10-27 14:56 ` Rogier Wolff
2000-10-28 13:15 ` Philipp Rumpf
2000-10-28 13:37 ` Brian Gerst
2000-10-28 13:53 ` Philipp Rumpf
2000-10-28 13:55 ` Brian Gerst
2000-10-28 15:05 ` Philipp Rumpf
2000-10-28 15:50 ` Brian Gerst
2000-10-28 16:10 ` Andrew Morton [this message]
2000-10-30 15:18 ` Philipp Rumpf
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=39FAFA68.A8250BA@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prumpf@parcelfarce.linux.theplanet.co.uk \
/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.