From: Stefan Haberland <sth@linux.ibm.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org,
Jan Hoeppner <hoeppner@linux.ibm.com>,
linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Colin Ian King <colin.i.king@gmail.com>
Subject: [PATCH 0/4] s390/dasd: fix out of bound access and other fixes
Date: Wed, 23 Nov 2022 17:07:15 +0100 [thread overview]
Message-ID: <20221123160719.3002694-1-sth@linux.ibm.com> (raw)
Hi Jens,
please apply the following patches that:
- fix an out of bound access
- fix a possible IO error on non-IBM storage
- fix a typo
- improve debug data for error scenarios
regards,
Stefan
Colin Ian King (1):
s390/dasd: Fix spelling mistake "Ivalid" -> "Invalid"
Stefan Haberland (3):
s390/dasd: increase printing of debug data payload
s390/dasd: fix no record found for raw_track_access
s390/dasd: fix possible buffer overflow in copy_pair_show
drivers/s390/block/dasd_devmap.c | 2 +-
drivers/s390/block/dasd_eckd.c | 43 ++++++++++++++++----------------
drivers/s390/block/dasd_ioctl.c | 2 +-
3 files changed, 23 insertions(+), 24 deletions(-)
--
2.34.1
next reply other threads:[~2022-11-23 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 16:07 Stefan Haberland [this message]
2022-11-23 16:07 ` [PATCH 1/4] s390/dasd: Fix spelling mistake "Ivalid" -> "Invalid" Stefan Haberland
2022-11-23 16:07 ` [PATCH 2/4] s390/dasd: increase printing of debug data payload Stefan Haberland
2022-11-23 16:07 ` [PATCH 3/4] s390/dasd: fix no record found for raw_track_access Stefan Haberland
2022-11-23 16:07 ` [PATCH 4/4] s390/dasd: fix possible buffer overflow in copy_pair_show Stefan Haberland
2022-11-23 17:37 ` [PATCH 0/4] s390/dasd: fix out of bound access and other fixes Jens Axboe
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=20221123160719.3002694-1-sth@linux.ibm.com \
--to=sth@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=colin.i.king@gmail.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hoeppner@linux.ibm.com \
--cc=linux-block@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox