Re: [PATCH 1/1 linux-next] ext4: add compatibility flag check

2016-11-24 Thread Fabian Frederick
> On 25 November 2016 at 06:26 Theodore Ts'o wrote: > > > On Thu, Nov 24, 2016 at 08:47:41PM +0100, Fabian Frederick wrote: > > data=journal mount option should disable O_DIRECT access > > (See Documentation/filesystems/ext4.txt) but open operations > > using

Re: [PATCH 1/1 linux-next] ext4: add compatibility flag check

2016-11-24 Thread Fabian Frederick
> On 25 November 2016 at 06:26 Theodore Ts'o wrote: > > > On Thu, Nov 24, 2016 at 08:47:41PM +0100, Fabian Frederick wrote: > > data=journal mount option should disable O_DIRECT access > > (See Documentation/filesystems/ext4.txt) but open operations > > using O_CREAT|O_RDWR|O_DIRECT|O_SYNC have

Re: [PATCH 1/1 linux-next] ext4: add compatibility flag check

2016-11-24 Thread Theodore Ts'o
On Thu, Nov 24, 2016 at 08:47:41PM +0100, Fabian Frederick wrote: > data=journal mount option should disable O_DIRECT access > (See Documentation/filesystems/ext4.txt) but open operations > using O_CREAT|O_RDWR|O_DIRECT|O_SYNC have no warning in return and file is > being > created. This patch

Re: [PATCH 1/1 linux-next] ext4: add compatibility flag check

2016-11-24 Thread Theodore Ts'o
On Thu, Nov 24, 2016 at 08:47:41PM +0100, Fabian Frederick wrote: > data=journal mount option should disable O_DIRECT access > (See Documentation/filesystems/ext4.txt) but open operations > using O_CREAT|O_RDWR|O_DIRECT|O_SYNC have no warning in return and file is > being > created. This patch

Re: [PATCH 1/1 linux-next] ext4: add compatibility flag check

2016-11-24 Thread Fabian Frederick
> On 24 November 2016 at 21:39 Al Viro wrote: > > > On Thu, Nov 24, 2016 at 08:47:41PM +0100, Fabian Frederick wrote: > > data=journal mount option should disable O_DIRECT access > > (See Documentation/filesystems/ext4.txt) but open operations > > using

Re: [PATCH 1/1 linux-next] ext4: add compatibility flag check

2016-11-24 Thread Fabian Frederick
> On 24 November 2016 at 21:39 Al Viro wrote: > > > On Thu, Nov 24, 2016 at 08:47:41PM +0100, Fabian Frederick wrote: > > data=journal mount option should disable O_DIRECT access > > (See Documentation/filesystems/ext4.txt) but open operations > > using O_CREAT|O_RDWR|O_DIRECT|O_SYNC have no

Re: [PATCH 1/1 linux-next] ext4: add compatibility flag check

2016-11-24 Thread Al Viro
On Thu, Nov 24, 2016 at 08:47:41PM +0100, Fabian Frederick wrote: > data=journal mount option should disable O_DIRECT access > (See Documentation/filesystems/ext4.txt) but open operations > using O_CREAT|O_RDWR|O_DIRECT|O_SYNC have no warning in return and file is > being > created. This patch

Re: [PATCH 1/1 linux-next] ext4: add compatibility flag check

2016-11-24 Thread Al Viro
On Thu, Nov 24, 2016 at 08:47:41PM +0100, Fabian Frederick wrote: > data=journal mount option should disable O_DIRECT access > (See Documentation/filesystems/ext4.txt) but open operations > using O_CREAT|O_RDWR|O_DIRECT|O_SYNC have no warning in return and file is > being > created. This patch

[PATCH 1/1 linux-next] ext4: add compatibility flag check

2016-11-24 Thread Fabian Frederick
data=journal mount option should disable O_DIRECT access (See Documentation/filesystems/ext4.txt) but open operations using O_CREAT|O_RDWR|O_DIRECT|O_SYNC have no warning in return and file is being created. This patch adds vfs super_operations compatibility flag function returning -EPERM in such

[PATCH 1/1 linux-next] ext4: add compatibility flag check

2016-11-24 Thread Fabian Frederick
data=journal mount option should disable O_DIRECT access (See Documentation/filesystems/ext4.txt) but open operations using O_CREAT|O_RDWR|O_DIRECT|O_SYNC have no warning in return and file is being created. This patch adds vfs super_operations compatibility flag function returning -EPERM in such