From: Jack Stone <jwjstone@fastmail.fm>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: at net/ipv4/tcp.c:1610 tcp_recvmsg+0xb1b/0xc70()
Date: Sat, 26 May 2012 12:22:09 +0100 [thread overview]
Message-ID: <4FC0BCE1.6070601@fastmail.fm> (raw)
In-Reply-To: <1337979331.10135.2.camel@edumazet-glaptop>
On 05/25/2012 09:55 PM, Eric Dumazet wrote:
> On Fri, 2012-05-25 at 22:45 +0200, Eric Dumazet wrote:
>> On Fri, 2012-05-25 at 21:25 +0100, Jack Stone wrote:
>>> Hi All,
>>>
>>> The following warning keeps hitting me. I couldn't get the first one - it had already left dmesg hence the W taint.
>>> The C taint is from r8712u from staging.
>>>
>>> I've seen it with 3.4.0-076444-g07acfc2 (recent Linus tree) and 3.4.0-rc3-00089-gc6f5c93.
>>>
>>> I am going to attempt to bisect it now.
>>
>> No need, update your tree.
>>
>>
>
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=1ca7ee30630e1022dbcf1b51be20580815ffab73
>
>
>
I'm still getting this with da89fb1 which includes the above
Linux hover1 3.4.0-07797-gda89fb1 #4 SMP Fri May 25 22:23:14 BST 2012 x86_64 x86_64 x86_64 GNU/Linux
next prev parent reply other threads:[~2012-05-26 11:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 20:25 WARNING: at net/ipv4/tcp.c:1610 tcp_recvmsg+0xb1b/0xc70() Jack Stone
2012-05-25 20:25 ` Jack Stone
2012-05-25 20:45 ` Eric Dumazet
2012-05-25 20:55 ` Eric Dumazet
2012-05-25 21:31 ` Jack Stone
2012-05-26 11:22 ` Jack Stone [this message]
2012-05-27 13:59 ` Eric Dumazet
2012-05-27 15:34 ` Jack Stone
2012-05-27 15:34 ` Jack Stone
2012-05-27 17:35 ` Eric Dumazet
2012-05-27 19:13 ` Jack Stone
2012-05-27 19:13 ` Jack Stone
2012-05-27 19:36 ` Eric Dumazet
2012-05-27 19:46 ` Eric Dumazet
2012-05-28 0:25 ` Eric Dumazet
2012-05-28 8:34 ` Jack Stone
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=4FC0BCE1.6070601@fastmail.fm \
--to=jwjstone@fastmail.fm \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.