netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: denys@visp.net.lb, netdev@vger.kernel.org
Subject: Re: [PATCH]: Schedule correct qdisc in watchdog.
Date: Tue, 19 Aug 2008 05:37:45 +0000	[thread overview]
Message-ID: <20080819053745.GA2722@ff.dom.local> (raw)
In-Reply-To: <20080818.165638.169012226.davem@davemloft.net>

On Mon, Aug 18, 2008 at 04:56:38PM -0700, David Miller wrote:
> From: Jarek Poplawski <jarkao2@gmail.com>
> Date: Mon, 18 Aug 2008 12:58:05 +0000
> 
> > On Mon, Aug 18, 2008 at 03:45:29PM +0300, Denys Fedoryshchenko wrote:
> > > Patch applied, got another warning.
> > 
> > I hope I'll figure this out before evening. Probably it's safer
> > to stop testing for a while.
> 
> We have to put the kfree() of the qdisc back into an RCU handler,
> that's all.

As a matter of fact, I still have some doubts about this. Top level
qdiscs must be deactivated before destroy and during this process we
make sure nothing can use them anymore. So, since this all is under
rtnl_lock(), I wonder if we really need this qdisc root_lock around
qdisc_destroy() for root qdiscs at all.

Maybe there are some common lists which depend on this and rtnl_lock
isn't enough for them. If so, maybe it's easier to change locking in
these places. But, of course, I can miss something.

I'm not against RCU here if it's really needed. Otherwise, this
destroying in softirq context, without rtnl_lock() looks like a
potential obstacle for the future.

Jarek P.

  reply	other threads:[~2008-08-19  5:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18  8:39 [PATCH]: Schedule correct qdisc in watchdog David Miller
2008-08-18  9:10 ` Jarek Poplawski
2008-08-18  9:31   ` David Miller
2008-08-18  9:47     ` Jarek Poplawski
2008-08-18 10:10       ` David Miller
2008-08-18 10:35         ` Jarek Poplawski
2008-08-18 10:43           ` Jarek Poplawski
2008-08-18 11:04             ` Denys Fedoryshchenko
2008-08-18 11:20               ` Jarek Poplawski
2008-08-18 11:35                 ` Jarek Poplawski
2008-08-18 12:45                   ` Denys Fedoryshchenko
2008-08-18 12:58                     ` Jarek Poplawski
2008-08-18 23:56                       ` David Miller
2008-08-19  5:37                         ` Jarek Poplawski [this message]
2008-08-19  5:39                           ` David Miller
2008-08-19  5:42                           ` Jarek Poplawski
2008-08-18 15:55                     ` Jarek Poplawski
2008-08-18 18:05                       ` Denys Fedoryshchenko
2008-08-19  3:54                   ` David Miller
2008-08-19  6:59                     ` Jarek Poplawski
2008-08-19  7:03                       ` David Miller
2008-08-18 11:06             ` Jarek Poplawski
2008-08-19  3:51               ` David Miller
2008-08-19  4:08                 ` David Miller

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=20080819053745.GA2722@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=davem@davemloft.net \
    --cc=denys@visp.net.lb \
    --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;
as well as URLs for NNTP newsgroup(s).