Re: [PATCH 1/1 linux-next] jfs: atomically read inode size

2017-01-24 Thread Dave Kleikamp
On 01/23/2017 01:52 PM, Fabian Frederick wrote: > > >> On 23 January 2017 at 19:43 Dave Kleikamp wrote: >> >> >> On 01/23/2017 11:50 AM, Fabian Frederick wrote: >>> See i_size_read() comments in include/linux/fs.h >> >> Is this fixing a real problem? Can the bd_inode

Re: [PATCH 1/1 linux-next] jfs: atomically read inode size

2017-01-24 Thread Dave Kleikamp
On 01/23/2017 01:52 PM, Fabian Frederick wrote: > > >> On 23 January 2017 at 19:43 Dave Kleikamp wrote: >> >> >> On 01/23/2017 11:50 AM, Fabian Frederick wrote: >>> See i_size_read() comments in include/linux/fs.h >> >> Is this fixing a real problem? Can the bd_inode size change while we're >>

Re: [PATCH 1/1 linux-next] jfs: atomically read inode size

2017-01-23 Thread Fabian Frederick
> On 23 January 2017 at 19:43 Dave Kleikamp wrote: > > > On 01/23/2017 11:50 AM, Fabian Frederick wrote: > > See i_size_read() comments in include/linux/fs.h > > Is this fixing a real problem? Can the bd_inode size change while we're > mounting or resizing the

Re: [PATCH 1/1 linux-next] jfs: atomically read inode size

2017-01-23 Thread Fabian Frederick
> On 23 January 2017 at 19:43 Dave Kleikamp wrote: > > > On 01/23/2017 11:50 AM, Fabian Frederick wrote: > > See i_size_read() comments in include/linux/fs.h > > Is this fixing a real problem? Can the bd_inode size change while we're > mounting or resizing the filesystem? > Behind good

Re: [PATCH 1/1 linux-next] jfs: atomically read inode size

2017-01-23 Thread Dave Kleikamp
On 01/23/2017 11:50 AM, Fabian Frederick wrote: > See i_size_read() comments in include/linux/fs.h Is this fixing a real problem? Can the bd_inode size change while we're mounting or resizing the filesystem? > > Signed-off-by: Fabian Frederick > --- > fs/jfs/resize.c | 4 ++--

Re: [PATCH 1/1 linux-next] jfs: atomically read inode size

2017-01-23 Thread Dave Kleikamp
On 01/23/2017 11:50 AM, Fabian Frederick wrote: > See i_size_read() comments in include/linux/fs.h Is this fixing a real problem? Can the bd_inode size change while we're mounting or resizing the filesystem? > > Signed-off-by: Fabian Frederick > --- > fs/jfs/resize.c | 4 ++-- >

[PATCH 1/1 linux-next] jfs: atomically read inode size

2017-01-23 Thread Fabian Frederick
See i_size_read() comments in include/linux/fs.h Signed-off-by: Fabian Frederick --- fs/jfs/resize.c | 4 ++-- fs/jfs/super.c | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/fs/jfs/resize.c b/fs/jfs/resize.c index bd9b641..7ddcb44 100644 ---

[PATCH 1/1 linux-next] jfs: atomically read inode size

2017-01-23 Thread Fabian Frederick
See i_size_read() comments in include/linux/fs.h Signed-off-by: Fabian Frederick --- fs/jfs/resize.c | 4 ++-- fs/jfs/super.c | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/fs/jfs/resize.c b/fs/jfs/resize.c index bd9b641..7ddcb44 100644 --- a/fs/jfs/resize.c +++