Re: [PATCH] Add explanation of I_DIRTY_DATASYNC bit

[Andreas Schwab]

Jan Kara <jack@xxxxxxx> writes:

> Add explanation of I_DIRTY_DATASYNC bit.
>
> Signed-off-by: Jan Kara <jack@xxxxxxx>
>
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index 56bd421..475125e 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -1280,7 +1280,10 @@ struct super_operations {
>   * Two bits are used for locking and completion notification, I_LOCK and I_SYNC.
>   *
>   * I_DIRTY_SYNC		Inode itself is dirty.
> - * I_DIRTY_DATASYNC	Data-related inode changes pending
> + * I_DIRTY_DATASYNC	Data-related inode changes pending. We keep track of
> + *		`	these changes separately from I_DIRTY_SYNC so that we
                ^

Looks like a typo.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@xxxxxxx
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
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/