From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: [RFC, PATCH] net: sock_queue_err_skb() and sk_forward_alloc corruption
Date: Mon, 07 Dec 2009 23:32:16 +0100 [thread overview]
Message-ID: <4B1D8270.20308@gmail.com> (raw)
In-Reply-To: <20091207090154.6bbfe8e2@nehalam>
While investigating on sk_forward_alloc corruptions, I found two problems :
1) skb_tstamp_tx() is calling sock_queue_err_skb().
This is not good as is, because we need sock lock
before calling sock_queue_err_skb().
Problem is skb_tstamp_rx() wont be able to lock sock...
skb_tstamp_rx() ->
sock_queue_err_skb() ->
sk_mem_charge(sk, skb->truesize) -> // PROBLEM :
sk->sk_forward_alloc -= size; // MUST BE PROTECTED
2) UDP (again) sk_forward_alloc corruption
__udp4_lib_err ->
if (inet->recverr)
ip_icmp_error() ->
sock_queue_err_skb() // PROBLEM
Oh well...
I wonder if we could use a special version of skb_set_owner_r()/sock_rfree()
*without* sk_mem_charge()/sk_mem_uncharge() calls for this error queue.
(We dont call sk_rmem_schedule() anyway, so I guess current usage is not correct,
even with sock locked ?)
Something like this (untested but compiled) patch ?
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
---
include/net/sock.h | 11 ++++++++++-
net/core/sock.c | 8 ++++++++
2 files changed, 18 insertions(+), 1 deletion(-)
diff --git a/include/net/sock.h b/include/net/sock.h
index 3f1a480..76277ce 100644
--- a/include/net/sock.h
+++ b/include/net/sock.h
@@ -961,6 +961,7 @@ extern struct sk_buff *sock_rmalloc(struct sock *sk,
gfp_t priority);
extern void sock_wfree(struct sk_buff *skb);
extern void sock_rfree(struct sk_buff *skb);
+extern void sock_nocharge_rfree(struct sk_buff *skb);
extern int sock_setsockopt(struct socket *sock, int level,
int op, char __user *optval,
@@ -1383,6 +1384,14 @@ static inline void skb_set_owner_r(struct sk_buff *skb, struct sock *sk)
sk_mem_charge(sk, skb->truesize);
}
+static inline void skb_set_owner_nocharge_r(struct sk_buff *skb, struct sock *sk)
+{
+ skb_orphan(skb);
+ skb->sk = sk;
+ skb->destructor = sock_nocharge_rfree;
+ atomic_add(skb->truesize, &sk->sk_rmem_alloc);
+}
+
extern void sk_reset_timer(struct sock *sk, struct timer_list* timer,
unsigned long expires);
@@ -1398,7 +1407,7 @@ static inline int sock_queue_err_skb(struct sock *sk, struct sk_buff *skb)
if (atomic_read(&sk->sk_rmem_alloc) + skb->truesize >=
(unsigned)sk->sk_rcvbuf)
return -ENOMEM;
- skb_set_owner_r(skb, sk);
+ skb_set_owner_nocharge_r(skb, sk);
skb_queue_tail(&sk->sk_error_queue, skb);
if (!sock_flag(sk, SOCK_DEAD))
sk->sk_data_ready(sk, skb->len);
diff --git a/net/core/sock.c b/net/core/sock.c
index 76ff58d..181a39a 100644
--- a/net/core/sock.c
+++ b/net/core/sock.c
@@ -1284,6 +1284,14 @@ void sock_rfree(struct sk_buff *skb)
}
EXPORT_SYMBOL(sock_rfree);
+void sock_nocharge_rfree(struct sk_buff *skb)
+{
+ struct sock *sk = skb->sk;
+
+ atomic_sub(skb->truesize, &sk->sk_rmem_alloc);
+}
+EXPORT_SYMBOL(sock_nocharge_rfree);
+
int sock_i_uid(struct sock *sk)
{
next prev parent reply other threads:[~2009-12-07 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 17:01 Fw: [Bug 14749] New: Kernel locks up after a few minutes of heavy surfing Stephen Hemminger
2009-12-07 17:05 ` Stephen Hemminger
2009-12-07 22:32 ` Eric Dumazet [this message]
2009-12-26 1:29 ` [RFC, PATCH] net: sock_queue_err_skb() and sk_forward_alloc corruption 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=4B1D8270.20308@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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.