Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-08-03 Thread Alan Curry
Christian Lamparter wrote: > > One thing I noticed in your previous post is that you "might" not have > draft-802.11n enabled. Do you see any "disabling HT/VHT due to WEP/TKIP use." > in your dmesg logs? If so, check if you can force your AP to use WPA2 > with CCMP/AES only. > Yes, I've had that

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-08-03 Thread Christian Lamparter
On Wednesday, August 3, 2016 3:49:26 AM CEST Alan Curry wrote: > Al Viro wrote: > > > > Which just might mean that we have *three* issues here - > > (1) buggered __copy_to_user_inatomic() (and friends) on some sparcs > > (2) your ssl-only corruption > > (3) Alan's x86_64 corruption on

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-08-02 Thread Alan Curry
Al Viro wrote: > > Which just might mean that we have *three* issues here - > (1) buggered __copy_to_user_inatomic() (and friends) on some sparcs > (2) your ssl-only corruption > (3) Alan's x86_64 corruption on plain TCP read - no ssl *or* sparc > anywhere, and no multi-segment r

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-27 Thread Al Viro
On Wed, Jul 27, 2016 at 08:26:48PM -0400, alexmcwhir...@triadic.us wrote: > I'm going to go ahead and say this is where my issue and the op's issue > begin to branch apart from one another. He's seeing this on all incoming > data, whereas i am only seeing it on ssl data and not on sun4v. > > At t

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-27 Thread alexmcwhirter
On 2016-07-27 20:31, Al Viro wrote: On Wed, Jul 27, 2016 at 04:45:43PM -0700, David Miller wrote: > I highly expect both my issue and OP's issue to revolve not around > commit e5a4b0bb803b specifically, but around other code that no longer > behaves as expected because of it. Indeed, and that

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-27 Thread Al Viro
On Wed, Jul 27, 2016 at 04:45:43PM -0700, David Miller wrote: > > I highly expect both my issue and OP's issue to revolve not around > > commit e5a4b0bb803b specifically, but around other code that no longer > > behaves as expected because of it. > > Indeed, and that fault address rounding bug oc

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-27 Thread David Miller
From: alexmcwhir...@triadic.us Date: Wed, 27 Jul 2016 19:02:40 -0400 > On 2016-07-27 14:04, alexmcwhir...@triadic.us wrote: >> Just to add some more information to this, the corruption seems to >> effect ssh as well. >> Using a sun hme interface, occasionally upon an ssh connection it will >> refu

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-27 Thread alexmcwhirter
On 2016-07-27 14:04, alexmcwhir...@triadic.us wrote: Just to add some more information to this, the corruption seems to effect ssh as well. Using a sun hme interface, occasionally upon an ssh connection it will refuse to authenticate a client with either password or cert authentication. Using wi

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-27 Thread alexmcwhirter
Just to add some more information to this, the corruption seems to effect ssh as well. Using a sun hme interface, occasionally upon an ssh connection it will refuse to authenticate a client with either password or cert authentication. Using wireshark to capture and decrypt the packets between

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-27 Thread Alan Curry
Al Viro wrote: > > Another thing (and if that works, it's *NOT* a proper fix - it would be > papering over the problem, but at least it would show where to look for > it) - try (on top of mainline) the following delta: I tried it on top of v4.6.4 and on top of the very recent v4.7-2509-g59ebc44 f

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-26 Thread Kalle Valo
alexmcwhir...@triadic.us writes: > On 2016-07-26 09:59, Christian Lamparter wrote: >> Thanks, I gave the program a try with my WNDA3100 and a WN821N v2 >> devices. >> I did not see any corruptions in any of the tests though. Can you >> tell me >> something about your wireless network too? I would

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-26 Thread Alan Curry
Christian Lamparter wrote: > Thanks, I gave the program a try with my WNDA3100 and a WN821N v2 devices. > I did not see any corruptions in any of the tests though. Can you tell me > something about your wireless network too? I would like to know what router > and firmware are you using? Also import

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-26 Thread alexmcwhirter
On 2016-07-26 09:59, Christian Lamparter wrote: Thanks, I gave the program a try with my WNDA3100 and a WN821N v2 devices. I did not see any corruptions in any of the tests though. Can you tell me something about your wireless network too? I would like to know what router and firmware are you u

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-26 Thread Christian Lamparter
On Tuesday, July 26, 2016 4:57:03 AM CEST Alan Curry wrote: > Al Viro wrote: > > On Sun, Jul 24, 2016 at 07:45:13PM +0200, Christian Lamparter wrote: > > > > > > The symptom is that downloaded files (http, ftp, and probably other > > > > protocols) have small corrupted segments (about 1-2 kilobyte

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-25 Thread Alan Curry
Al Viro wrote: > On Sun, Jul 24, 2016 at 07:45:13PM +0200, Christian Lamparter wrote: > > > > The symptom is that downloaded files (http, ftp, and probably other > > > protocols) have small corrupted segments (about 1-2 kilobytes long) in > > > random locations. Only downloads that sustain a high

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-25 Thread alexmcwhirter
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 gr

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-25 Thread Alan Curry
Christian Lamparter wrote: > > As for carl9170: I'm not sure what the driver or firmware can do about > this at this time. You can try to disable the hardware crypto by setting > nohwcrypt via the module option. However, this might not do anything at all. The nohwcrypt parameter didn't make any d

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-24 Thread Al Viro
On Sun, Jul 24, 2016 at 07:45:13PM +0200, Christian Lamparter wrote: > > The symptom is that downloaded files (http, ftp, and probably other > > protocols) have small corrupted segments (about 1-2 kilobytes long) in > > random locations. Only downloads that sustain a high speed for at least a > >

Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-24 Thread Christian Lamparter
Hello, I added Al Viro to the CC (probably not necessary...) On Sunday, July 24, 2016 3:35:14 AM CEST Alan Curry wrote: > [1.] One line summary of the problem: > network data corruption (bisected to e5a4b0bb803b) > > [2.] Full description of the problem/report: > Note: although

PROBLEM: network data corruption (bisected to e5a4b0bb803b)

2016-07-23 Thread Alan Curry
[1.] One line summary of the problem: network data corruption (bisected to e5a4b0bb803b) [2.] Full description of the problem/report: Note: although my bisect ended at a commit from before 3.19, I have the same symptom in all newer kernels I've tried, up to 4.6.4. The commit was: &g