Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751953AbbKJINV (ORCPT ); Tue, 10 Nov 2015 03:13:21 -0500 Received: from mx2.suse.de ([195.135.220.15]:45394 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751339AbbKJINO (ORCPT ); Tue, 10 Nov 2015 03:13:14 -0500 From: Hannes Reinecke To: Jens Axboe Cc: Alexander Graf , Christoph Hellwig , Ming Lei , linux-kernel@vger.kernel.org, Hannes Reinecke Subject: [PATCHv3 0/4] loop: enable different physical blocksizes Date: Tue, 10 Nov 2015 09:13:06 +0100 Message-Id: <1447143190-44589-1-git-send-email-hare@suse.de> X-Mailer: git-send-email 1.8.5.6 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1352 Lines: 38 Currently the loop driver just simulates 512-byte blocks. When creating bootable images on virtual machines it might be required to use a different physical blocksize (eg 4k for S/390 DASD), as the some bootloaders (like lilo or zipl for S/390) need to know the physical block addresses of the kernel and initrd. This patchset extends the current LOOP_SET_STATUS64 ioctl to set the logical and physical blocksize by re-using the existing 'init' fields, which are currently unused. As usual, comments and reviews are welcome. Changes to v1: - Move LO_FLAGS_BLOCKSIZE definition - Reshuffle patches Changes to v2: - Drop lo_flags setting in loop_set_fd as suggested by Ming Lei Hannes Reinecke (4): loop: Enable correct physical blocksize loop: Remove unused 'bdev' argument from loop_set_capacity loop: Add 'lo_logical_blocksize' loop: Pass logical blocksize in 'lo_init[0]' ioctl field drivers/block/loop.c | 41 ++++++++++++++++++++++++++++++++++------- drivers/block/loop.h | 1 + include/uapi/linux/loop.h | 1 + 3 files changed, 36 insertions(+), 7 deletions(-) -- 1.8.5.6 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/