Re: [PATCH 1/9] staging/lustre/llite: Access to released file trigsa restore

[Greg Kroah-Hartman]

"trigs"?  Come on, we don't have a lack of characters here...

On Tue, Nov 19, 2013 at 09:23:40PM +0800, Peng Tao wrote:
> From: JC Lafoucriere <jacques-charles.lafoucriere@xxxxxx>
> 
> When a client accesses data in a released file,
> or truncate it, client must trig a restore request.
> During this restore, the client must not glimpse and
> must use size from MDT. To bring the "restore is running"
> information on the client we add a new t_state bit field
> to mdt_info which will be used to carry transient file state.
> To memorise this information in the inode we add a new flag
> LLIF_FILE_RESTORING.
> 
> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3432
> Lustre-change: http://review.whamcloud.com/6537
> Signed-off-by: JC Lafoucriere <jacques-charles.lafoucriere@xxxxxx>
> Reviewed-by: Oleg Drokin <oleg.drokin@xxxxxxxxx>
> Tested-by: Oleg Drokin <oleg.drokin@xxxxxxxxx>
> Signed-off-by: Peng Tao <bergwolf@xxxxxxxxx>
> Signed-off-by: Andreas Dilger <andreas.dilger@xxxxxxxxx>
> ---
>  drivers/staging/lustre/lustre/include/cl_object.h  |    6 ++-
>  .../lustre/lustre/include/lustre/lustre_idl.h      |   14 +++--
>  drivers/staging/lustre/lustre/lclient/lcommon_cl.c |    6 +++
>  drivers/staging/lustre/lustre/llite/file.c         |   39 +++++++++++++-
>  .../staging/lustre/lustre/llite/llite_internal.h   |    3 ++
>  drivers/staging/lustre/lustre/llite/llite_lib.c    |   36 +++++++++++++
>  drivers/staging/lustre/lustre/llite/vvp_io.c       |   54 ++++++++++++++++++--
>  drivers/staging/lustre/lustre/lov/lov_io.c         |   15 ++++--
>  .../staging/lustre/lustre/ptlrpc/pack_generic.c    |    2 +-
>  drivers/staging/lustre/lustre/ptlrpc/wiretest.c    |   17 +++---
>  10 files changed, 168 insertions(+), 24 deletions(-)

This patch has checkpatch errors, sorry, please fix them before sending
them again.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/