public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Julian Anastasov <ja@ssi.bg>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org, kain@kain.org
Subject: Re: OOPS: Multipath routing 2.4.17
Date: Sat, 2 Mar 2002 00:05:35 +0100	[thread overview]
Message-ID: <20020302000535.B16807@wotan.suse.de> (raw)
In-Reply-To: <p73sn7jkixm.fsf@oldwotan.suse.de> <Pine.LNX.4.44.0203020050220.1706-100000@u.domain.uli>
In-Reply-To: <Pine.LNX.4.44.0203020050220.1706-100000@u.domain.uli>

On Sat, Mar 02, 2002 at 01:01:25AM +0000, Julian Anastasov wrote:
> 
> 	How oops is reached:

[... see my other crossing mail...]
> 	If I understand correctly the locking (please correct me),
> we can have many threads at the same time:
> 
> - many in ip_route_* calling fib_select_multipath
> 
> - one in rtnetlink playing with nh_*

Yes, that's correct.

-Andi


  reply	other threads:[~2002-03-01 23:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0203012316120.1420-100000@u.domain.uli.suse.lists.linux.kernel>
2002-03-01 22:43 ` OOPS: Multipath routing 2.4.17 Andi Kleen
2002-03-02  1:01   ` Julian Anastasov
2002-03-01 23:05     ` Andi Kleen [this message]
2002-03-01 23:00 ` Andi Kleen
2002-03-02  1:20   ` Julian Anastasov
2002-03-02  0:27 Julian Anastasov
2002-03-02  0:25 ` Kain
2002-03-02 12:59 ` kuznet
2002-03-02 15:28   ` Julian Anastasov
2002-03-02 14:36     ` kuznet
2002-03-02 18:10       ` Julian Anastasov
     [not found] <20020301173414.GA30037@kain.org.suse.lists.linux.kernel>
2002-03-01 18:12 ` Andi Kleen
2002-03-01 19:04   ` Kain
  -- strict thread matches above, loose matches on Subject: below --
2002-03-01 17:34 Kain

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=20020302000535.B16807@wotan.suse.de \
    --to=ak@suse.de \
    --cc=ja@ssi.bg \
    --cc=kain@kain.org \
    --cc=linux-kernel@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