Re: [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

On 11/01/2016 03:02 PM, Christoph Hellwig wrote: On Mon, Oct 31, 2016 at 08:37:19PM +0100, Hannes Reinecke wrote: The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Can we

Re: [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

On 11/01/2016 03:02 PM, Christoph Hellwig wrote: On Mon, Oct 31, 2016 at 08:37:19PM +0100, Hannes Reinecke wrote: The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Can we

Re: [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

On 11/01/2016 03:02 PM, Christoph Hellwig wrote: On Mon, Oct 31, 2016 at 08:37:19PM +0100, Hannes Reinecke wrote: The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Can we

Re: [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

On 11/01/2016 03:02 PM, Christoph Hellwig wrote: On Mon, Oct 31, 2016 at 08:37:19PM +0100, Hannes Reinecke wrote: The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Can we

Re: [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

On Mon, Oct 31, 2016 at 08:37:19PM +0100, Hannes Reinecke wrote: > The current LOOP_SET_STATUS64 ioctl has two unused fields > 'init[2]', which can be used in conjunction with the > LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Can we give them sane field names while at it? Also

Re: [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

On Mon, Oct 31, 2016 at 08:37:19PM +0100, Hannes Reinecke wrote: > The current LOOP_SET_STATUS64 ioctl has two unused fields > 'init[2]', which can be used in conjunction with the > LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Can we give them sane field names while at it? Also

[PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Signed-off-by: Hannes Reinecke --- drivers/block/loop.c | 24 +++- 1 file changed, 19

[PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Signed-off-by: Hannes Reinecke --- drivers/block/loop.c | 24 +++- 1 file changed, 19 insertions(+), 5

Re: [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

Hi Hannes, Hannes Reinecke writes: > The current LOOP_SET_STATUS64 ioctl has two unused fields > 'init[2]', which can be used in conjunction with the > LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. I don't see a reason to set LO_FLAGS_BLOCKSIZE inside of the

Re: [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

Hi Hannes, Hannes Reinecke writes: > The current LOOP_SET_STATUS64 ioctl has two unused fields > 'init[2]', which can be used in conjunction with the > LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. I don't see a reason to set LO_FLAGS_BLOCKSIZE inside of the

[PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Signed-off-by: Hannes Reinecke --- drivers/block/loop.c | 25 - 1 file changed, 20 insertions(+),

[PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Signed-off-by: Hannes Reinecke --- drivers/block/loop.c | 25 - 1 file changed, 20

[PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Signed-off-by: Hannes Reinecke --- drivers/block/loop.c | 14 -- 1 file changed, 12 insertions(+), 2

[PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Signed-off-by: Hannes Reinecke h...@suse.de --- drivers/block/loop.c | 14 -- 1 file changed, 12 insertions(+),

[PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Signed-off-by: Hannes Reinecke --- drivers/block/loop.c | 14 -- 1 file changed, 12 insertions(+), 2

[PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field

The current LOOP_SET_STATUS64 ioctl has two unused fields 'init[2]', which can be used in conjunction with the LO_FLAGS_BLOCKSIZE flag to pass in the new logical blocksize. Signed-off-by: Hannes Reinecke h...@suse.de --- drivers/block/loop.c | 14 -- 1 file changed, 12 insertions(+),