From: Eric Dumazet <dada1@cosmosbay.com>
To: David Miller <davem@davemloft.net>
Cc: ilpo.jarvinen@helsinki.fi, netdev@vger.kernel.org
Subject: Re: net-next/unix: BUG: using smp_processor_id() in preemptible
Date: Mon, 24 Nov 2008 06:51:06 +0100 [thread overview]
Message-ID: <492A40CA.1070005@cosmosbay.com> (raw)
In-Reply-To: <20081123.173426.255648175.davem@davemloft.net>
David Miller a écrit :
> From: David Miller <davem@davemloft.net>
> Date: Sun, 23 Nov 2008 17:20:14 -0800 (PST)
>
>> From: Eric Dumazet <dada1@cosmosbay.com>
>> Date: Sun, 23 Nov 2008 04:32:30 +0100
>>
>>> [PATCH] net: make sock_prot_inuse_add() preempt safe
> ...
>> Eric, you added this bug by starting to use this interface in
>> situations where BH's were not disabled.
>>
>> Ever existing use adhered to that rule.
>>
>> If you therefore want to call this interface in new locations,
>> you have to make sure those locations follow the rule too.
>
> Here is what I commited to fix this bug.
>
> net: Make sure BHs are disabled in sock_prot_inuse_add()
>
> The rule of calling sock_prot_inuse_add() is that BHs must
> be disabled. Some new calls were added where this was not
> true and this tiggers warnings as reported by Ilpo.
>
> Fix this by adding explicit BH disabling around those call sites.
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---
> net/netlink/af_netlink.c | 3 +++
> net/sctp/socket.c | 4 ++++
> net/unix/af_unix.c | 2 ++
> 3 files changed, 9 insertions(+), 0 deletions(-)
Hello David
Thanks for working on this during my sleep ;)
next prev parent reply other threads:[~2008-11-24 5:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 21:04 net-next/unix: BUG: using smp_processor_id() in preemptible Ilpo Järvinen
2008-11-23 3:32 ` Eric Dumazet
2008-11-23 21:40 ` Ilpo Järvinen
2008-11-24 1:20 ` David Miller
2008-11-24 1:34 ` David Miller
2008-11-24 5:51 ` Eric Dumazet [this message]
2008-11-24 8:01 ` Eric Dumazet
2008-11-24 8:09 ` David Miller
2008-11-24 8:41 ` Ilpo Järvinen
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=492A40CA.1070005@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--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 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.