> Does the test_thread_flag(TIF_IA32) macro only return true for a 32-bit > user-space process running within a 64-bit user space environment > (perhaps I can do away with the check in the autofs daemon, perhaps it > doesn't quite work correctly)?
Hm... If we fix it in the user level that would also be OK, I suppose... > Oh .. so maybe the answer to my question is yes? It is - we check *only* for the process, that is to receive the packet. > What about other arches offer 32-bit within a 64-bit environment (has > this been the case on sparc64 at some point)? > What about the compiler padding on these? We have no technical ability to check this. First I wanted to get your opinion about this particular fix for x86 machines. As far as sparc(64) and other 32-to-64 are concerned - I can start talking to their users/maintainers to check. > Don't get me wrong, I'm not against fixing this, in fact I'd like to, > but I'm concerned it may end up a bit of a can of worms. _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
