Hi Al,

We've hit the situation a few times where a corrupt symlink could easily 
oops the kernel.  The problem was tracked down to an older e2fsutils 
that didn't do much sanity checking on symlinks during a fsck.  This 
patch uses strnlen when reading in the symlink and ensures that it 
doesn't exceed PATH_MAX.

Would you accept this kind of 'hardening'?

Signed-off-by: Mike Waychison <mikew@google.com>