From: Jens Axboe <axboe@kernel.dk>
To: Stefan Haberland <sth@linux.ibm.com>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Colin Ian King <colin.i.king@gmail.com>,
linux-s390@vger.kernel.org, Jan Hoeppner <hoeppner@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
linux-block@vger.kernel.org
Subject: Re: [PATCH 0/4] s390/dasd: fix out of bound access and other fixes
Date: Wed, 23 Nov 2022 10:37:54 -0700 [thread overview]
Message-ID: <166922507445.2259.6403259573928080506.b4-ty@kernel.dk> (raw)
In-Reply-To: <20221123160719.3002694-1-sth@linux.ibm.com>
On Wed, 23 Nov 2022 17:07:15 +0100, Stefan Haberland wrote:
> 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
>
> [...]
Applied, thanks!
[1/4] s390/dasd: Fix spelling mistake "Ivalid" -> "Invalid"
commit: 4ba5f0c36cfdda68347269c02961cd90f8443ace
[2/4] s390/dasd: increase printing of debug data payload
commit: b49e648fcca7e420c4ad670a548e19f0e8531c30
[3/4] s390/dasd: fix no record found for raw_track_access
commit: 590ce6d96d6a224b470a3862c33a483d5022bfdb
[4/4] s390/dasd: fix possible buffer overflow in copy_pair_show
commit: 7e8a05b47ba7200f333eefd19979eeb4d273ceec
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-11-23 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 16:07 [PATCH 0/4] s390/dasd: fix out of bound access and other fixes Stefan Haberland
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 ` Jens Axboe [this message]
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=166922507445.2259.6403259573928080506.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=borntraeger@linux.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 \
--cc=sth@linux.ibm.com \
/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