On Tue, Apr 16, 2013 at 10:44:33AM +0200, Jan Schmidt wrote:
> On Tue, April 16, 2013 at 10:40 (+0200), Liu Bo wrote:
> > We need such a sanity check for wrong start, otherwise, even with
> > a wrong start that's larger than file size, we can end up not only
> > changing inode's force compress flag
On Tue, April 16, 2013 at 10:40 (+0200), Liu Bo wrote:
> We need such a sanity check for wrong start, otherwise, even with
> a wrong start that's larger than file size, we can end up not only
> changing inode's force compress flag but also FS's incompat flags.
That reads out very cryptic. Can you
We need such a sanity check for wrong start, otherwise, even with
a wrong start that's larger than file size, we can end up not only
changing inode's force compress flag but also FS's incompat flags.
Signed-off-by: Liu Bo
---
fs/btrfs/ioctl.c | 11 +++
1 files changed, 7 insertions(+),
