From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, dsahern@gmail.com,
valdis.kletnieks@vt.edu, idosch@mellanox.com
Subject: Re: [PATCH net-next] ipv6: addrconf: fix a lockdep splat
Date: Tue, 07 Nov 2017 10:52:26 +0900 (KST) [thread overview]
Message-ID: <20171107.105226.460231522106716516.davem@davemloft.net> (raw)
In-Reply-To: <1510006409.2849.88.camel@edumazet-glaptop3.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Mon, 06 Nov 2017 14:13:29 -0800
> From: Eric Dumazet <edumazet@google.com>
>
> Fixes a case where GFP_ATOMIC allocation must be used instead of
> GFP_KERNEL one.
...
> Fixes: f3d9832e56c4 ("ipv6: addrconf: cleanup locking in ipv6_add_addr")
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Reported-by: Valdis Kletnieks <valdis.kletnieks@vt.edu>
Applied, thanks.
prev parent reply other threads:[~2017-11-07 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 22:13 [PATCH net-next] ipv6: addrconf: fix a lockdep splat Eric Dumazet
2017-11-07 0:50 ` David Ahern
2017-11-07 1:52 ` David Miller [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=20171107.105226.460231522106716516.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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).