Peter Staubach <[email protected]> writes:
> One other thing -- it doesn't seem particularly correct to me to just
> silently truncate the symbolic link contents.
Sure, and 2.6 indeed returns ENAMETOOLONG. I was just trying to close
the problem and not change the functionality in 2.4. If the consensus
is that we should change it to return an error, I can certainly cook
up patches for that.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] nfs client, kernel 2.4.31: readlink result overflow
- Re: [PATCH] nfs client, kernel 2.4.31: readlink result overflow
- Re: [PATCH] nfs client, kernel 2.4.31: readlink result overflow
- Re: [PATCH] nfs client, kernel 2.4.31: readlink result overflow
- Re: [PATCH] nfs client, kernel 2.4.31: readlink result overflow
- Re: [PATCH] nfs client, kernel 2.4.31: readlink result overflow
- Re: [PATCH] nfs client, kernel 2.4.31: readlink result overflow
- Re: [PATCH] nfs client, kernel 2.4.31: readlink result overflow
- Re: [PATCH] nfs client, kernel 2.4.31: readlink result overflow
- Re: [PATCH] nfs client, kernel 2.4.31: readlink result overflow
- Re: [PATCH] nfs client, kernel 2.4.31: readlink result overflow
- Re: [PATCH] nfs client, kernel 2.4.31: readlink result overflow
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|