linux-kernel - Re: [PATCH 4/4] loop: Pass logical blocksize in 'lo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20161101140208.GC16815@lst.de>
Date:   Tue, 1 Nov 2016 15:02:08 +0100
From:   Christoph Hellwig <hch@....de>
To:     Hannes Reinecke <hare@...e.de>
Cc:     Jens Axboe <axboe@...com>, Christoph Hellwig <hch@....de>,
        Alexander Graf <agraf@...e.com>, Ming@...e.de,
        "Lei <tom.leiming"@gmail.com, linux-kernel@...r.kernel.org
Subject: 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 I see now reason
not to merge this with the previous two patches.