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
| ||
|
Date: Thu, 7 May 2020 17:22:28 +0200 From: Stefan Haberland <sth@...ux.ibm.com> To: Christoph Hellwig <hch@....de> Cc: axboe@...nel.dk, linux-block@...r.kernel.org, hoeppner@...ux.ibm.com, linux-s390@...r.kernel.org, heiko.carstens@...ibm.com, gor@...ux.ibm.com, borntraeger@...ibm.com, linux-kernel@...r.kernel.org, Peter Oberparleiter <oberpar@...ux.ibm.com> Subject: Re: [PATCH 1/1] s390/dasd: remove ioctl_by_bdev from DASD driver Am 06.05.20 um 06:52 schrieb Christoph Hellwig: > > No, I mean the series that I actually sent out: > > https://lkml.org/lkml/2020/4/21/66 > https://lkml.org/lkml/2020/4/21/68 > https://lkml.org/lkml/2020/4/21/69 OK, just thought again about your suggestion and also that you have already been talking about a symbol lookup I just have written a prototype that took your first two patches as base, exports the symbol of dasd_biodasdinfo and in ibm.c I do a kallsyms_lookup_name("dasd_biodasdinfo"). So I would not have to define a structure twice or rely on MAJORs. Also we would not have to define an own file operation only for DASD devices. What do you think about this? If you agree I will polish the patches, test them and send them for review.
Powered by blists - more mailing lists