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
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
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
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
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
