mirror of
https://git.openafs.org/openafs.git
synced 2025-01-31 05:27:44 +00:00
d80485cd95
Currently, h_stateVerifyHost verifies that all of the valid entries on h->z.interface are on the host address hashtable. If we don't have a h->z.interface, we check the primary address h->z.host/h->z.port instead. But if we do have a h->z.interface, we don't check h->z.host/h->z.port at all. Normally, the primary address should always be included in the h->z.interface list (in a 'valid==1' entry), and so checking the primary address is redundant. However, currently it is possible in some edge cases for the primary address to be missing from the hashtable and to not be listed as a valid address in h->z.interface. In such cases, we don't flag an error or even log a warning, since we don't check the primary address separately. (These cases are bugs, and will be addressed in future commits.) To detect this case, change h_stateVerifyHost to always check h->z.host, just like we do for the entries in h->z.interface. Reviewed-on: https://gerrit.openafs.org/15070 Tested-by: BuildBot <buildbot@rampaginggeek.com> Reviewed-by: Mark Vitale <mvitale@sinenomine.net> Reviewed-by: Marcio Brito Barbosa <mbarbosa@sinenomine.net> Reviewed-by: Cheyenne Wills <cwills@sinenomine.net> Reviewed-by: Michael Meffie <mmeffie@sinenomine.net> Reviewed-by: Benjamin Kaduk <kaduk@mit.edu> (cherry picked from commit 9d144491d94e7e19e2d710601a37045ef1ef1fdc) Change-Id: Icdd65c081372e1057df67401643973e1ac6f016e Reviewed-on: https://gerrit.openafs.org/15509 Tested-by: BuildBot <buildbot@rampaginggeek.com> Reviewed-by: Andrew Deason <adeason@sinenomine.net> Reviewed-by: Michael Meffie <mmeffie@sinenomine.net> Reviewed-by: Mark Vitale <mvitale@sinenomine.net> Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
AFS is a distributed file system that enables users to share and access all of the files stored in a network of computers as easily as they access the files stored on their local machines. The file system is called distributed for this exact reason: files can reside on many different machines, but are available to users on every machine. OpenAFS 1.0 was originally released by IBM under the terms of the IBM Public License 1.0 (IPL10). For details on IPL10 see the LICENSE file in this directory. The current OpenAFS distribution is licensed under a combination of the IPL10 and many other licenses as granted by the relevant copyright holders. The LICENSE file in this directory contains more details, thought it is not a comprehensive statement. See INSTALL for information about building and installing OpenAFS on various platforms. See CODING for developer information and guidelines. See NEWS for recent changes to OpenAFS.