Re: [PATCH] nfsd4_lock() returns bogus values to clients

On Sun, Dec 25, 2005 at 06:49:33AM +0000, Al Viro wrote:
> From: Al Viro <[email protected]>
> Date: 1135493243 -0500
> 
> missing nfserror() in default case of a switch by return value of
> posix_lock_file(); as the result we send negative host-endian to
> clients that expect positive network-endian, preferably mentioned
> in RFC...  BTW, that case is not impossible - posix_lock_file()
> can return -ENOLCK and we do not handle that one explicitly.

Gaack...  s/nfserror/nfserrno/, of course...
-
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] nfsd/vfs.c: endianness fixes
    • From: Al Viro <[email protected]>
  • [PATCH] nfsd4_lock() returns bogus values to clients
    • From: Al Viro <[email protected]>

• Prev by Date: Re: [ANNOUNCE][RFC] PlugSched-6.1.6 for 2.6.15-rc5 and 2.6.15-rc5-mm2
• Next by Date: Re: [Question] LinuxThreads, setuid - Is there user mode hook?
• Previous by thread: [PATCH] nfsd4_lock() returns bogus values to clients
• Next by thread: FS possible security exposure ?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]