From: Dave Jones <davej@redhat.com>
To: netdev@vger.kernel.org
Cc: Fedora Kernel Team <kernel-team@fedoraproject.org>
Subject: Re: WARNING: at net/ipv4/tcp.c:1598 tcp_recvmsg+0x641/0xd30()
Date: Fri, 10 Aug 2012 16:29:10 -0400 [thread overview]
Message-ID: <20120810202910.GA19359@redhat.com> (raw)
In-Reply-To: <20120806154616.GB2187@redhat.com>
On Mon, Aug 06, 2012 at 11:46:16AM -0400, Dave Jones wrote:
> We just got an automated report of this WARN being hit in 3.5
>
> > backtrace:
> > :WARNING: at net/ipv4/tcp.c:1598 tcp_recvmsg+0x641/0xd30()
> > :Hardware name: P5Q DELUXE
> > :recvmsg bug: copied 99F66400 seq 99F6A4A8 rcvnxt 99F6CDAD fl 0
> > : [<ffffffff811848e6>] do_sync_read+0xe6/0x120
> > : [<ffffffff81275eea>] ? inode_has_perm.isra.31.constprop.61+0x2a/0x30
> > : [<ffffffff81272f32>] ? security_file_permission+0x92/0xb0
> > : [<ffffffff81184d81>] ? rw_verify_area+0x61/0xf0
> > : [<ffffffff811852cd>] vfs_read+0x15d/0x180
> > : [<ffffffff8118533a>] sys_read+0x4a/0x90
> > : [<ffffffff8160fc29>] system_call_fastpath+0x16/0x1b
>
> 1594 /* Now that we have two receive queues this
> 1595 * shouldn't happen.
> 1596 */
> 1597 if (WARN(before(*seq, TCP_SKB_CB(skb)->seq),
> 1598 "recvmsg bug: copied %X seq %X rcvnxt %X fl %X\n",
> 1599 *seq, TCP_SKB_CB(skb)->seq, tp->rcv_nxt,
> 1600 flags))
> 1601 break;
>
>
> Hopefully this means more to you guys than it does to me.
We're getting more reports of this happening too.
This guy managed to hit both of the recvmsg BUG's.
https://bugzilla.redhat.com/show_bug.cgi?id=846996
https://bugzilla.redhat.com/show_bug.cgi?id=846991
The first reporter claimed to be doing nothing special, just browsing with google chrome.
Anyone ?
Dave
next prev parent reply other threads:[~2012-08-10 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 15:46 WARNING: at net/ipv4/tcp.c:1598 tcp_recvmsg+0x641/0xd30() Dave Jones
2012-08-10 20:29 ` Dave Jones [this message]
2012-08-10 20:40 ` Eric Dumazet
2012-08-20 16:20 ` Dave Jones
2012-08-20 16:42 ` 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=20120810202910.GA19359@redhat.com \
--to=davej@redhat.com \
--cc=kernel-team@fedoraproject.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 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).