Re: [PATCH] cifs: fix broken oplock handling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 17 Sep 2010 18:56:39 +0530
Suresh Jayaraman <sjayaraman@xxxxxxx> wrote:

> cifs_new_fileinfo() does not use the 'oplock' value from the callers. Instead,
> it sets it to REQ_OPLOCK which seems wrong. We should be using the oplock value
> obtained from the Server to set the inode's clientCanCacheAll or
> clientCanCacheRead flags. Fix this by passing oplock from the callers to
> cifs_new_fileinfo().
> 
> This change dates back to commit a6ce4932 (2.6.30-rc3). So, all the affected
> versions will need this fix. Please Cc stable once reviewed and accepted.
> 
> Cc: Jeff Layton <jlayton@xxxxxxxxxx>
> Signed-off-by: Suresh Jayaraman <sjayaraman@xxxxxxx>

Looks correct to me:

Reviewed-by: Jeff Layton <jlayton@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux