"H. Peter Anvin" wrote:

quoted

Hi there,

We just suffered some SCSI bus problems on kernel.org that resulted in
significant data loss on our mirror volume, but not enough to ditch
the whole filesystem and start over (rsync --checksum is a good
thing.)  However, we keep getting oopses, ostensibly as the result of
a garbaged symlink.  This filesystem has been run through fsck -y
(e2fstools 1.26).

Oops details at:

    http://userweb.kernel.org/~hpa/oops-20020516/

The kernel running is 2.4.19-pre8.

I assume that was `fsck -fy'?

You seem have a 4k symlink.   I'd have expected fsck to detect that.

It crashed because vfs_readlink ran off the end of the page.

--- linux-2.4.19-pre8/fs/namei.c	Thu May  2 17:44:56 2002
+++ linux-akpm/fs/namei.c	Thu May 16 19:34:57 2002

@@ -1947,7 +1947,7 @@ int vfs_readlink(struct dentry *dentry, 
 	if (IS_ERR(link))
 		goto out;
 
-	len = strlen(link);
+	len = strnlen(link, PAGE_CACHE_SIZE);
 	if (len > (unsigned) buflen)
 		len = buflen;
 	if (copy_to_user(buffer, link, len))