From: Jesper Dangaard Brouer <brouer@redhat.com>
To: David Miller <davem@davemloft.net>, Pravin B Shelar <pshelar@nicira.com>
Cc: brouer@redhat.com,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Anupam Chanda <achanda@vmware.com>,
Tom Herbert <tom@herbertland.com>, Andrew Vagin <avagin@odin.com>
Subject: bisect: bug X11 not working for SSH on net-next commit 6ae459bda
Date: Fri, 2 Oct 2015 09:52:12 +0200 [thread overview]
Message-ID: <20151002095212.7b47869c@redhat.com> (raw)
Hi DaveM,
Could you please merge git tree net into net-next.
Running on a kernel based on net-next (at commit 4bf1b54f9df) made my
SSH stopped forwarding X11.
Bisected the problem down to commit 6ae459bda ("skbuff: Fix skb
checksum flag on skb pull"), which seems to have been fixed in git
tree "net" by commit 31b33dfb0a14 ("skbuff: Fix skb checksum partial
check.").
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
keywords: X11 SSH csum checksum bug IPv6 connect error loopback broken
reply other threads:[~2015-10-02 7:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20151002095212.7b47869c@redhat.com \
--to=brouer@redhat.com \
--cc=achanda@vmware.com \
--cc=avagin@odin.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=tom@herbertland.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;
as well as URLs for NNTP newsgroup(s).