Re: cgd aes rump tests failing

[Rin Okuyama <rokuyama%rk.phys.keio.ac.jp@localhost>]

On 2016/11/29 16:48, Martin Husemann wrote:
> On Tue, Nov 29, 2016 at 07:31:26AM +0000, Alexander Nasonov wrote:
> > I can't do much without access to hardware and the tests running
> > once a week.
> >
> > The tests fail inside write_testvec which calls rump_sys_lseek(0,
> > SEEK_SET) and rump_sys_write(512). One of them returns EINVAL.
>
> I don't know what to look at or how to debug it.
>
> Does rump inherit securelevel from the host kernel?

I tried it on my AlphaServer DS10 (userland and kernel from today's
current). Then, all the cgd tests passed except for 2 expected-failure
cases. What's the difference between mine and yours??

Thanks,
Rin
====
% uname -a
NetBSD ds10 7.99.43 NetBSD 7.99.43 (DS10) #0: Tue Nov 29 17:25:29 JST 2016  rin@xxx:xxx alpha
% sysctl -a | grep securelevel
kern.securelevel = 1
security.models.bsd44.securelevel = 1
security.models.securelevel.name = Traditional NetBSD: Securelevel
security.models.securelevel.securelevel = 1
% cd /usr/tests/dev/cgd && atf-run | atf-report
Tests root: /usr/tests/dev/cgd

t_cgd_3des (1/4): 2 test cases
    cgd_3des_cbc_192_encblkno1: [0.135891s] Passed.
    cgd_3des_cbc_192_encblkno8: [0.115210s] Passed.
[0.254371s]

t_cgd_aes (2/4): 8 test cases
    cgd_aes_cbc_128_encblkno1: [0.114576s] Passed.
    cgd_aes_cbc_128_encblkno8: [0.115417s] Passed.
    cgd_aes_cbc_192_encblkno1: [0.116881s] Passed.
    cgd_aes_cbc_192_encblkno8: [0.122155s] Passed.
    cgd_aes_cbc_256_encblkno1: [0.115024s] Passed.
    cgd_aes_cbc_256_encblkno8: [0.116398s] Passed.
    cgd_aes_xts_256: [0.106214s] Expected failure: aes-xts implementation not committed yet: /var/build/src/tests/dev/cgd/t_cgd_aes.c:3522: configure_cgd(cgdfd, dkpath, "aes-xts", "encblkno1", aes_xts_256_key, sizeof(aes_xts_256_key)): Invalid argument
    cgd_aes_xts_512: [0.105140s] Expected failure: aes-xts implementation not committed yet: /var/build/src/tests/dev/cgd/t_cgd_aes.c:3576: configure_cgd(cgdfd, dkpath, "aes-xts", "encblkno1", aes_xts_512_key, sizeof(aes_xts_512_key)): Invalid argument
[0.920841s]

t_cgd_blowfish (3/4): 6 test cases
    cgd_bf_cbc_128_encblkno1: [0.115654s] Passed.
    cgd_bf_cbc_128_encblkno8: [0.116552s] Passed.
    cgd_bf_cbc_256_encblkno1: [0.116730s] Passed.
    cgd_bf_cbc_256_encblkno8: [0.116175s] Passed.
    cgd_bf_cbc_448_encblkno1: [0.121927s] Passed.
    cgd_bf_cbc_448_encblkno8: [0.115180s] Passed.
[0.708778s]

t_cgd (4/4): 3 test cases
    basic: [0.625301s] Passed.
    unaligned_write: [1.709333s] Passed.
    wrongpass: [0.731835s] Passed.
[3.071425s]

Test cases for known bugs:
    t_cgd_aes:cgd_aes_xts_256: aes-xts implementation not committed yet:
                               /var/build/src/tests/dev/cgd/t_cgd_aes.c:3522:
                               configure_cgd(cgdfd, dkpath, "aes-xts",
                               "encblkno1", aes_xts_256_key,
                               sizeof(aes_xts_256_key)): Invalid argument
    t_cgd_aes:cgd_aes_xts_512: aes-xts implementation not committed yet:
                               /var/build/src/tests/dev/cgd/t_cgd_aes.c:3576:
                               configure_cgd(cgdfd, dkpath, "aes-xts",
                               "encblkno1", aes_xts_512_key,
                               sizeof(aes_xts_512_key)): Invalid argument

Summary for 4 test programs:
    17 passed test cases.
    0 failed test cases.
    2 expected failed test cases.
    0 skipped test cases.