Hi Christoph, thanks for addressing this. But I must say that I do not like this approach. I get your point why you want this ioctl to be removed and I agree with that. Having those implicit partitions at all is really ugly but I fear that this is widely used int the field. So I can not simply remove this code although I would like to. Maybe we find a way to deprecate this. But anyway... Forcing the driver to be build in may have a lot of implications which we should at least have a look at and maybe discuss with the distributors. All major distributions have the driver build as modules and use module parameters in the initrd for example. The second thing is that I do not really like this s390-specific blockdevice operation. I can imagine some ways to get rid of this ioctl_by_bdev. Maybe having a udev rule to add a partition from userspace or having the driver add the implicit partition at the end. Or maybe something else. If it is OK I will have a look at this and discuss this issue with my colleagues and come up with a different approach. Regards, Stefan Am 21.04.20 um 08:12 schrieb Christoph Hellwig: > Hi Jens and DASD maintainers, > > can you take a look at this series, which stops the DASD driver from > issuing ioctls from kernel space, in preparation of removing > ioctl_by_bdev. I don't really like the new s390-only method, but short > of forcing the dasd driver to be built into the kernel I can't think of > anything better. But maybe the s390 maintainers are fine with forcing > the DASD driver to be built in, in which case we could go down that > route?
