On February 8, 2016 3:30 PM, Darren Tucker wrote: > To: Randall S. Becker <rsbecker@xxxxxxxxxxxxx> > Cc: OpenSSH Devel List <openssh-unix-dev@xxxxxxxxxxx> > Subject: Re: [Bug] Regression problem in transfer.sh for OpenSSH 7.1 P2 on > HPE NSE above dd-size 32k > > On Tue, Feb 9, 2016 at 6:36 AM, Randall S. Becker > <rsbecker@xxxxxxxxxxxxx> wrote: > [...] > > Getting detailed debug logs of the regression test would also really > > help here. Anyone have any pointers on where I can look to try to resolve > this? > > The logs should be in the regress directory. There should be ssh.log and > ssh.log for the currently running test and failed-ssh.log and failed-sshd.log > containing the concatenation of the logs from any failed tests. You can run > "make t-exec LTESTS=transfer" to run just that single test while you're playing > around to save some time. > > I have seen something similar on old FreeBSD systems when the test was run > on an NFS mount. I never figured out why this was, but running the test on > local disk worked in that case. So here's where the 5% comes in. The dd code explicitly checks SSIZE_MAX on the platform and restricts the obs values that are legitimate. From limits.h on NSE: #define SSIZE_MAX 53248 /* max single I/O size, 52K */ The result is that dd is failing parameter checks above 32k, so 64k, 128k, and 256k are invalid and should have been omitted on the platform in any event. Is this a legit bug in the OpenSSH regression suite? Cheers, Randall _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
