netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: subashab@codeaurora.org
To: netdev@vger.kernel.org
Cc: eric.dumazet@gmail.com
Subject: [PATCH] rps: Handle double list_add at __napi_schedule
Date: Mon, 15 Jun 2015 21:46:38 -0000	[thread overview]
Message-ID: <21d3b5e617ed44d217ce7f82e9fafa06.squirrel@www.codeaurora.org> (raw)

When NAPI_STATE_SCHED state is not set, enqueue_to_backlog()
will queue an IPI and add the backlog queue to the poll list. A packet
added by RPS onto the core could also add the NAPI backlog struct to the
poll list. This double addition to the list causes a crash -

2920.540304:   <2> list_add double add: new=ffffffc076ed2930,
prev=ffffffc076ed2930, next=ffffffc076ed2850.
   [<ffffffc000460dd4>] __list_add+0xcc/0xf0
2921.064962:   <2> [<ffffffc000b44880>] rps_trigger_softirq+0x1c/0x40
2921.070779:   <2> [<ffffffc000284a14>]
generic_smp_call_function_single_interrupt+0xe8/0x12c
2921.078678:   <2> [<ffffffc00020d9ac>] handle_IPI+0x8c/0x1ec
2921.083796:   <2> [<ffffffc000200714>] gic_handle_irq+0x94/0xb0

Fix this race for double addition to list by checking the NAPI state.

Acked-by: Sharat Masetty <smasetty@qti.qualcomm.com>
Signed-off-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>

diff --git a/net/core/dev.c b/net/core/dev.c
index 6f561de..57d6d39 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -3225,7 +3225,8 @@ static void rps_trigger_softirq(void *data)
 {
        struct softnet_data *sd = data;

-       ____napi_schedule(sd, &sd->backlog);
+       if (!test_bit(NAPI_STATE_SCHED, &sd->backlog.state))
+               ____napi_schedule(sd, &sd->backlog);
        sd->received_rps++;
 }

             reply	other threads:[~2015-06-15 21:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 21:46 subashab [this message]
2015-06-15 23:24 ` [PATCH] rps: Handle double list_add at __napi_schedule Eric Dumazet

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=21d3b5e617ed44d217ce7f82e9fafa06.squirrel@www.codeaurora.org \
    --to=subashab@codeaurora.org \
    --cc=eric.dumazet@gmail.com \
    --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).