Re: OpenAFS 1.8.X token problems
Mark Vitale <[email protected]>
| Newsgroups | gmane.comp.file-systems.openafs.general |
|---|---|
| Message-ID | <[email protected]> |
Florian, > On May 22, 2019, at 5:39 PM, Mark Vitale <[email protected]> wrote: > > On May 22, 2019, at 4:56 PM, Mark Vitale <[email protected]> wrote: >> >> >> Before we go any further with that, I would like you to verify that all the OpenAFS components are the same version. Please provide the output from the following commands: >> - rxdebug <client> 7001 -version >> - strings $(which aklog) | grep OpenAFS >> - strings $(which tokens) | grep OpenAFS > > I forgot to ask for one other thing. After you have issued aklog and ostensibly have a token, please provide the output for the following command: > > - cat /proc/fs/openafs/unixusers I no longer need any of these; I've duplicated the problem and identified the root cause. The OpenAFS 1.8.x token interface fails for cell names with three (3) letters. This is because the VIOC_GETTOK2 pioctl may take either a cell name or an integer number. The code unfortunately assumes that any input with a length of 4 is an integer number, and follows a different code path. A cell name of three letters + a terminating nul fools this code into following the integer input path. It ends up trying to find the 'ifm' = x69606d00 = 1767320256th token for this user. Of course this is nonsensical; the code's safety limits cause a failure long before this is reached. I've begun working on a fix and will notify you when it's available on gerrit.openafs.org for review. Regards, -- Mark Vitale [email protected]