All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy.lkml@free.fr>
To: kuznet@ms2.inr.ac.ru
Cc: Willy Tarreau <willy.LKml@free.fr>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.2.1[78] : RTNETLINK lock not properly locking ?
Date: Thu, 23 Nov 2000 07:14:32 +0100 (MET)	[thread overview]
Message-ID: <974960072.3a1cb5c821d96@imp.free.fr> (raw)
In-Reply-To: <200011221809.VAA20851@ms2.inr.ac.ru>
In-Reply-To: <200011221809.VAA20851@ms2.inr.ac.ru>

> It is linux-2.2, guy. 8) "threads" are not threaded there.
> 
> Semaphores (rtnl_lock, particularly) protects only areas, which
> are going to _schedule_ excplicitly or implicitly.

ok, thanks a lot Alexey, now I understand.

> Please, read comments. People used to consider comments as something
> decorative, but they are not. 

I did read them again and again, but you know, when there's something
you don't understand, sometimes you interprete things badly.

> Any questions?
not anymore, of course :-)

> Sorry...
> 
> /* NOTE: these locks are not interrupt safe, are not SMP safe,
>  * they are even not atomic. 8)8)8) ... and it is not a bug.
> etc.
> 
> Do you call this "very precautios"? 8)

I spoke about the first ones :)

thanks a lot, now I know how to proceed.

Cheers,
Willy
-
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/

      reply	other threads:[~2000-11-23  6:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22  9:39 [BUG] 2.2.1[78] : RTNETLINK lock not properly locking ? Willy Tarreau
2000-11-22  9:46 ` David S. Miller
2000-11-22 11:27   ` Willy Tarreau
2000-11-22 11:27     ` David S. Miller
2000-11-22 15:36       ` Willy Tarreau
2000-11-22 18:09 ` kuznet
2000-11-23  6:14   ` Willy Tarreau [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=974960072.3a1cb5c821d96@imp.free.fr \
    --to=willy.lkml@free.fr \
    --cc=kuznet@ms2.inr.ac.ru \
    --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 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.