Converting SMB1 tests to SMB2
slow at samba.org
Tue Dec 3 14:20:29 UTC 2019
sorry for late reply, but I've got my head wrapped in
On 11/26/19 5:09 PM, Noel Power wrote:
> On 26/11/2019 11:45, Ralph Boehme via samba-technical wrote:
>> On 11/22/19 4:27 PM, Noel Power wrote:
>>> With this in mind I only create 'shallow copies' of the test envs that
>>> have tests that fail against the new default environments which don't
>>> support negotiation of SMB1.
>> These won't work in make test. You need at least IP addresses.
> yes that is true, however I am not sure even if these days make test
> normally will work (or if anyone actually even use it instead of autobuild)
> certainly during the python3 transition I am sure make test couldn't
> work as tests in the same job even were interfering with each other
> resulting in some tests split across various jobs. I would nearly bet
> there are currently tests that if all run together with a 'raw' make
> test would fail, I'd try it except I never ever had make test work for
> me anyway.
as pointed out by Andrew as well: we need to keep this working or at
least now make it worse. :)
>>> There are quite a few tests in the skip file that really are SMB1 only
>>> tests, in this case
>>> a) move the test from '_smb1' env to '_smb1_done' env
>> Just beware of tests where SMB1 is just the transport and the test tests
>> FSA layer logic, eg unlink.
> ? not entirely sure what you mean here, I guess what I was referring to
> there are many tests in the skip file that already have both SMB1 & >=
> SMB2 tests where the test name just differs in some indicator of the
> protocol used e.g. test.something.NT1 & test.something.SMB2, in these
> cases nothing needs to be happen other than just mark the test done
ok, looks like I misunderstood your initial statement so just ignore my
>>> In both cases the skip_smb1_fail file is updated with comments saying
>>> the test
>>> has been processed
>>> Currently ~70 tests have been 'processed' trivially in that branch. I
>>> fear that the work there might be wasted (if the wrong approach is being
>>> followed) so really it would be great to get this nailed down before
>>> more complex changes happen
>> Stepping back a little I think we only need the following:
>> 1. The file with the list of failing tests should not be used as a skip
>> list. Just maintain a private branch with the changes needed to generate
>> the list. The list can go into master as eg selftest/smb1-todo or
>> similarily named.
>> Ideally the commit that adds the list also included instructions and the
>> patchset as file that is needed to regenerate the list on sn-devel.
> currently the skip file is effectively documentation, the commits around
> this at the start of the patch set are just to prove it was a valid list
> (after migrating the envs to default only negotiate >= SMB2)
Ah, sorry, I missed the 'Revert "selftest: exclude SMB1 tests that fail
from tests"' commit.
> There are no 'changes' to generate the the list of skip tests other than
> making all envs by default not negotiate SMB1 and then trying to see
> what fails (and unfortunately this isn't as straight forward as running
> the tests with FAIL_IMMEDIATELY=0 as some tests hang etc.
Sure. Btw, how did you figure out which tests hang? Do you have a list
of those? I imagine only a few tests will hang, luckily most of them
because it's in one of the AD DC envs where we don't have to disable
SMB1 as discussed in MR
Ideally we can make the skiplist a knownfail list. Then every commit
that moves a failing test to a new *_smb1 env can comment out the list
> So I am not sure which changes you mean should be in a private branch. I
> guess I misunderstand what you mean
Nevermind. I was referring at changes like disabling smb1 in the envs.
>> 2. Don't disable SMB1 in the ad_dc_ntvfs fileserver. This also applies
>> when generating the todo list in step 1.
>> 3. Reduce the number of envs that use the s4 NTVFS fileserver. This will
>> get us rid of a few failing tests from the list. I'm currently running
>> pipeplines with patches that implement this:
>> With 2 and 3 together ~200 test will be removed from the list:
> I know you mentioned previously ignoring for the moment ad_dc_ntvfs
> tests but I had already identified the ones failing already so I didn't
> see the harm in having them in the skip file (and having the environment
> to run them) as they need to be dealt with eventually.
> However If it helps to reduce environments then of course removing them
> entirely makes sense.
> Removing ad_dc_ntvfs from the mix afaics removes ~10 environments e.g.
> directly dependant
> indirectly dependant
of these only ad_dc_ntvfs, s4member and rpc_proxy should still use the
s4 NTVFS fileserver, all other should use s3 smbd. Alongside, these
three envs will remain with smb1 enabled.
And most tests that fail against any of the other environments with smb1
disabled needs checking why this happens and not just be moved to a
*_smb1 env. Eg "samba4.blackbox.kinit_trust(fl2008r2dc_smb1:local)"
seems to check some kerberos stuff, so this shouldn't be affected by
disabling smb1. As there are only a few of those test failing in these
envs, we should investigate this upfront.
>> $ egrep 'ad_dc_ntvfs|ad_dc_default|ad_dc_slowtest|chgdc'
>> selftest/skip_smb1_fails | wc -l
>> 4. Add three new envs that support smb1: ad_dc_smb1, ad_member_smb1,
>> fileserver_smbd1, maybe more if featurewise required.
> when you say adding envs do you mean just 'shallow' copies or do we
> really need to try and go the extra mile to make these new environments
> properly independent (my previous attempt failed and it looked like
> perhaps alot of changes could ripple from trying this for little gain
> since the environments will be removed)
yes, just normal/full envs.
> also afaics instead of 3 we probably need 8 unless you mean some tests
> can be moved from existing envs to one of the above
Yes, we should move/consolidate as much as possible.
I'd start with the smbtorture tests and move the in a microcommits fashion.
Running make -j test TESTS=".*smb1" > tests.log 2>&1
on your branch from MR902 on sn-devel and processing the log to see
which smb1 envs are used, I get
$ cat tests.log | sed 's/.*(\(.*\)).*/\1/' tests.txt | \
sed s/:local// | sed s/:client// | sort -u
Of these only
are really needed plus possibly nt4_dc_smb1 to avoid many changes to
As for the other ones, given my MR to tweask the AD DC envs gets merged:
ad_dc_default_smb1 -> should be an alias to ad_dc_smb1
ad_dc_ntvfs_smb1 -> not needed, ad_dc_ntvfs has smb1 enabled
ad_dc_slowtests_smb1 -> not needed, failing tests must be fixed upfront
chgdcpass_smb1 -> not needed, failing tests must be fixed upfront
fl2000dc_smb1 -> not needed, failing tests must be fixed upfront
fl2003dc_smb1 -> not needed, failing tests must be fixed upfront
fl2008r2dc_smb1 -> not needed, failing tests must be fixed upfront
maptoguest_smb1 -> not needed, failing tests must be fixed upfront
nt4_dc_schannel_smb1 -> not needed, failing tests must be fixed upfront
nt4_member_smb1 -> fix tests upfront
rpc_proxy_smb1 -> not needed, still has smb1
s4member_smb1 -> dito
simpleserver_smb1 -> move tests to fileserver env
vampire_dc_smb1 -> fix tests upfront
>> 5. Add coresspondong _smb1_done alias envs.
>> 6. Go through the todo list, either
>> a) just fixing the test if it should genuinely
>> work with smb2 => remove test from todo list
>> b) convert failing smb1 tests to use the
>> envs from 4 => update used test env in todo list
> I guess this answers my question above wrt. above
>> Step 6 can be spread across volunteers.
>> 7. When the list is fully processed and all remaining tests on the todo
>> list that still need smb1 use one of the new _smb1 envs, disable smb1 in
>> all other envs except ad_dc_ntvfs and s4member.
> I don't like that disabling smb1 by default for the 'normal'
> environments is now a final step,
yeah, that's true, but I see no other way. We must split
e50b9b9ebddef304caf232c92b8fc83bc1003b1e into pieces, so I don't see a
way without breaking bisectabiliry having smb1 disabled in the envs
causing test failures in the commit series.
> that isn't as nice as starting from an
> initial point where we can clearly see what runs >=SMB2 and what
> doesn't, not only see but actually know (because the default env setup
> would prevent any accidently SMB1 usage) and similarly when you port a
> test you know it isn't still using some SMB1 that you didn't notice.
Well, we'll notice at the end and are forces to fixup then anyway.
is another example of a test failure that must be investigated instead
of adding a new env.
Ralph Boehme, Samba Team https://samba.org/
Samba Developer, SerNet GmbH https://sernet.de/en/samba/
More information about the samba-technical