From: David Miller <davem@davemloft.net>
To: kuznet@ms2.inr.ac.ru
Cc: dim@openvz.org, netdev@vger.kernel.org, dev@sw.ru
Subject: Re: [PATCH] fix sk->sk_filter field access
Date: Wed, 30 Aug 2006 16:16:17 -0700 (PDT) [thread overview]
Message-ID: <20060830.161617.85689252.davem@davemloft.net> (raw)
In-Reply-To: <20060830231406.GA25736@ms2.inr.ac.ru>
From: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Date: Thu, 31 Aug 2006 03:14:06 +0400
> > Let us to fix bugs first, and then consider rewriting the locking.
>
> To be honest, I think switching to RCU is the simplest bug fix.
> At least, it does not require to search where bh_lock_sock() is taken
> dn_queue_skb(), if it is not forgotten at all. :-)
Ok :-)
It is just that, I will have a hard time convincing people that this
is legitimate for 2.6.18, and we would like the bug to be fixed there.
next prev parent reply other threads:[~2006-08-30 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 13:07 [PATCH] fix sk->sk_filter field access Dmitry Mishin
2006-08-30 21:30 ` David Miller
2006-08-30 22:20 ` Alexey Kuznetsov
2006-08-30 22:32 ` David Miller
2006-08-30 23:14 ` Alexey Kuznetsov
2006-08-30 23:16 ` David Miller [this message]
2006-08-31 22:29 ` 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=20060830.161617.85689252.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dev@sw.ru \
--cc=dim@openvz.org \
--cc=kuznet@ms2.inr.ac.ru \
--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).