From: Stefan Haberland <sth@linux.ibm.com>
To: hch@lst.de
Cc: axboe@kernel.dk, hoeppner@linux.ibm.com,
linux-s390@vger.kernel.org, heiko.carstens@de.ibm.com,
gor@linux.ibm.com, linux-kernel@vger.kernel.org,
borntraeger@de.ibm.com
Subject: [PATCH v3 0/3] s390/dasd: remove ioctl_by_bdev from DASD driver
Date: Fri, 8 May 2020 15:14:52 +0200 [thread overview]
Message-ID: <20200508131455.55407-1-sth@linux.ibm.com> (raw)
Hi Christoph,
as discussed yesterday I have picked your first patch, adopted the second
one and created a new third patch to remove the ioctl_by_bdev calls.
I export the symbol for the dasd_biodasdinfo function and obtain the
pointer with a kallsyms_lookup_name.
The checking if the gendisk is owned by a DASD is done by comparing the
fops pointer as you suggested. Looks like the most suitable method here.
Please note that this patch is not ready for inclusion and only basic
function tested. It is just for discussion.
Christoph Hellwig (2):
dasd: refactor dasd_ioctl_information
block: add a s390-only biodasdinfo method
Stefan Haberland (1):
s390/dasd: remove ioctl_by_bdev calls
block/partitions/ibm.c | 15 +++++++--
drivers/s390/block/dasd_int.h | 1 +
drivers/s390/block/dasd_ioctl.c | 59 ++++++++++++++++++++++++---------
include/linux/blkdev.h | 1 +
4 files changed, 57 insertions(+), 19 deletions(-)
--
2.17.1
next reply other threads:[~2020-05-08 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 13:14 Stefan Haberland [this message]
2020-05-08 13:14 ` [PATCH v3 1/3] dasd: refactor dasd_ioctl_information Stefan Haberland
2020-05-08 13:14 ` [PATCH v3 2/3] block: add a s390-only biodasdinfo method Stefan Haberland
2020-05-08 15:53 ` Christoph Hellwig
2020-05-08 13:14 ` [PATCH v3 3/3] s390/dasd: remove ioctl_by_bdev calls Stefan Haberland
2020-05-08 15:53 ` Christoph Hellwig
2020-05-11 16:30 ` Stefan Haberland
2020-05-16 15:43 ` Christoph Hellwig
2020-05-18 8:13 ` Stefan Haberland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200508131455.55407-1-sth@linux.ibm.com \
--to=sth@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=hoeppner@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.