Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Jens Axboe <axboe@kernel.dk>
To:     Carlos Llamas <cmllamas@google.com>, linux-block@vger.kernel.org
Cc:     Christoph Hellwig <hch@lst.de>, kernel-team@android.com,
        linux-kernel@vger.kernel.org
In-Reply-To: <20220329201815.1347500-1-cmllamas@google.com>
References: <20220329201815.1347500-1-cmllamas@google.com>
Subject: Re: [PATCH] loop: fix ioctl calls using compat_loop_info
Message-Id: <164865210886.39485.16982992188546747372.b4-ty@kernel.dk>
Date:   Wed, 30 Mar 2022 08:55:08 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 29 Mar 2022 20:18:15 +0000, Carlos Llamas wrote:
> Support for cryptoloop was deleted in commit 47e9624616c8 ("block:
> remove support for cryptoloop and the xor transfer"), making the usage
> of loop_info->lo_encrypt_type obsolete. However, this member was also
> removed from the compat_loop_info definition and this breaks userspace
> ioctl calls for 32-bit binaries and CONFIG_COMPAT=y.
> 
> This patch restores the compat_loop_info->lo_encrypt_type member and
> marks it obsolete as well as in the uapi header definitions.
> 
> [...]

Applied, thanks!

[1/1] loop: fix ioctl calls using compat_loop_info
      commit: f941c51eeac7ebe0f8ec30943bf78e7f60aad039

Best regards,
-- 
Jens Axboe