From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-next] sk->sk_dst_lock inconsistent lock state
Date: Mon, 16 Dec 2013 21:53:39 +0300 [thread overview]
Message-ID: <20131216185339.GA2319@swordfish> (raw)
In-Reply-To: <1387201524.19078.227.camel@edumazet-glaptop2.roam.corp.google.com>
On (12/16/13 05:45), Eric Dumazet wrote:
> On Mon, 2013-12-16 at 12:04 +0300, Sergey Senozhatsky wrote:
> > Hello,
> >
> > 3.13.0-rc4-next-20131216
>
> This is the third time we have this report.
>
sorry.
nice, thanks for the info.
-ss
> http://patchwork.ozlabs.org/patch/301382/
>
> Thanks
>
>
prev parent reply other threads:[~2013-12-16 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 9:04 [linux-next] sk->sk_dst_lock inconsistent lock state Sergey Senozhatsky
2013-12-16 13:45 ` Eric Dumazet
2013-12-16 18:53 ` Sergey Senozhatsky [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=20131216185339.GA2319@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).