All of lore.kernel.org
 help / color / mirror / Atom feed
From: alexmcwhirter@triadic.us
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Alan Curry <rlwinm@sdf.org>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)
Date: Tue, 26 Jul 2016 00:38:51 -0400	[thread overview]
Message-ID: <5ad66efb31d2febc2a4fda0be591815b@triadic.us> (raw)
In-Reply-To: <1659922.nTqITfJpFk@debian64>

> Thanks for the detailed bug-report. I looked around the web to see if 
> it
> was already reported or not. If found that this issue was reported 
> before:
> [0], [1] and [2] by the same person (CC'ed). One difference is that the
> reporter had this issue with rsync on multiple SPARC systems. I ran a
> git grep on a 4.7.0-rc7+ (wt-2016-07-21-15-g97bd3b0). But it didn't 
> find
> any patches directly referencing the commit. I'm not sure if this issue
> has been fixed by now or not. I would greatly appreciate any comment
> about this from the "people of netdev" (Al Viro? Alex Mcwhirter?).

I can confirm the issue i was having with this commit still exists on 
sparc with the latest mainline kernel.

      parent reply	other threads:[~2016-07-26  4:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24  3:35 PROBLEM: network data corruption (bisected to e5a4b0bb803b) Alan Curry
2016-07-24 17:45 ` Christian Lamparter
2016-07-24 17:45   ` Christian Lamparter
2016-07-24 19:02   ` Al Viro
2016-07-24 19:02     ` Al Viro
2016-07-26  4:57     ` Alan Curry
2016-07-26 13:59       ` Christian Lamparter
2016-07-26 18:15         ` alexmcwhirter
2016-07-27  6:39           ` Kalle Valo
2016-07-27  1:14         ` Alan Curry
2016-07-27 10:32     ` Alan Curry
2016-07-27 18:04       ` alexmcwhirter
2016-07-27 23:02         ` alexmcwhirter
2016-07-27 23:45           ` David Miller
2016-07-28  0:31             ` Al Viro
2016-07-28  0:26               ` alexmcwhirter
2016-07-28  1:22                 ` Al Viro
2016-07-28  1:22                   ` Al Viro
2016-08-03  3:49                   ` Alan Curry
2016-08-03 12:43                     ` Christian Lamparter
2016-08-03 23:25                       ` Alan Curry
     [not found]                     ` <20160803054118.GG2356@ZenIV.linux.org.uk>
     [not found]                       ` <2363167.YiBS7sFNO2@debian64>
     [not found]                         ` <20160809145836.GQ2356@ZenIV.linux.org.uk>
     [not found]                           ` <20170210081126.GA14157@ZenIV.linux.org.uk>
2017-02-10 21:45                             ` Al Viro
2017-02-11 19:37                               ` Christian Lamparter
2017-02-12  5:42                                 ` Al Viro
2017-02-13 21:56                                   ` Christian Lamparter
2017-02-14  1:33                                     ` [PATCH][CFT] Saner error handling in skb_copy_datagram_iter() et.al. (was Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)) Al Viro
2017-02-17 15:54                                       ` [PATCH][CFT] Saner error handling in skb_copy_datagram_iter() et.al David Miller
2017-02-17 17:03                                         ` Al Viro
2017-02-18  0:02                                           ` Al Viro
2017-02-18  2:24                                             ` Al Viro
2017-02-19 19:19                                             ` Christian Lamparter
2017-02-20 15:14                                             ` David Miller
2017-02-21 13:25                                             ` David Laight
2016-07-26  4:32   ` PROBLEM: network data corruption (bisected to e5a4b0bb803b) Alan Curry
2016-07-26  4:38   ` alexmcwhirter [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=5ad66efb31d2febc2a4fda0be591815b@triadic.us \
    --to=alexmcwhirter@triadic.us \
    --cc=chunkeey@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rlwinm@sdf.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.