From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tom Parkin <tparkin@katalix.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: LOCKDEP complaints in l2tp_xmit_skb()
Date: Thu, 28 Jun 2012 17:23:43 +0200 [thread overview]
Message-ID: <1340897023.13187.109.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120628152010.GC2507@raven>
On Thu, 2012-06-28 at 16:20 +0100, Tom Parkin wrote:
> Ha, yes, fair enough ;-)
>
> FWIW, I'm no longer seeing splat #1 from my previous report, but I do
> still see splat #2. Since they both ended up tripping over in
> l2tp_xmit_skb() I had assumed they were symptoms of the same root
> cause -- my mistake.
>
Fixing the #2 issue should be easy, I think.
I'll send an official submission asap for #1
thanks
prev parent reply other threads:[~2012-06-28 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 11:11 LOCKDEP complaints in l2tp_xmit_skb() Tom Parkin
2012-06-28 6:56 ` Eric Dumazet
2012-06-28 8:57 ` Eric Dumazet
2012-06-28 11:22 ` Eric Dumazet
2012-06-28 14:33 ` Tom Parkin
2012-06-28 15:00 ` Eric Dumazet
2012-06-28 15:20 ` Tom Parkin
2012-06-28 15:23 ` Eric Dumazet [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=1340897023.13187.109.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tparkin@katalix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox