From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
"Jason J . Herne" <jjherne@linux.vnet.ibm.com>,
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 0/2] 3270 improvements
Date: Thu, 21 Sep 2017 12:22:30 +0200 [thread overview]
Message-ID: <8abd41f8-e3fd-682f-1669-a5c3870c32fd@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170921112459.0153cc64.cohuck@redhat.com>
On 09/21/2017 11:24 AM, Cornelia Huck wrote:
> On Wed, 20 Sep 2017 19:23:12 +0200
> Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
>
>> Jason found some problems with 3270 which he traced down to insufficient
>> output buffer size. I've looked into the underlying issue (and the
>> relevant code) and I saw strange things. Among others an unreasonable
>> assert requiring the payload of a ccw being less than some more or
>> less arbitrary limit (dictated by the size of the output buffer).
>>
>> Because we were already considering converting 3270 to CcwDataStream I've
>> decided to try do get rid of this strange limitation on the length of the
>> writes too.
>>
>> This series depends on my IDA work, which can be found here:
>> https://lists.nongnu.org/archive/html/qemu-devel/2017-09/msg03434.html.
>>
>> Halil Pasic (2):
>> s390x/3270: IDA support for 3270 via CcwDataStream
>> s390x/3270: handle writes of arbitrary length
>>
>> hw/char/terminal3270.c | 46 +++++++++++++++++++++++++++------------------
>> hw/s390x/3270-ccw.c | 4 ++--
>> include/hw/s390x/3270-ccw.h | 5 ++---
>> 3 files changed, 32 insertions(+), 23 deletions(-)
>>
>
> Are you planning to do some further work on 3270, btw?
>
I did not. I jumped in because of IDA, and because I did
not agree with increasing the buffer size to another arbitrary
an value (and essentially keep the bug). I hope the original
authors will do further polishing.
I'm just curious, what's behind the question?
Halil
next prev parent reply other threads:[~2017-09-21 10:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 17:23 [Qemu-devel] [PATCH 0/2] 3270 improvements Halil Pasic
2017-09-20 17:23 ` [Qemu-devel] [PATCH 1/2] s390x/3270: IDA support for 3270 via CcwDataStream Halil Pasic
2017-09-21 9:15 ` Cornelia Huck
2017-09-21 11:22 ` Halil Pasic
2017-09-21 12:05 ` Cornelia Huck
2017-09-21 16:11 ` Halil Pasic
2017-09-22 13:38 ` Cornelia Huck
2017-09-20 17:23 ` [Qemu-devel] [PATCH 2/2] s390x/3270: handle writes of arbitrary length Halil Pasic
2017-09-21 9:23 ` Cornelia Huck
2017-09-21 10:30 ` Halil Pasic
2017-09-20 18:22 ` [Qemu-devel] [PATCH 0/2] 3270 improvements no-reply
2017-09-21 9:24 ` Cornelia Huck
2017-09-21 10:22 ` Halil Pasic [this message]
2017-09-21 10:48 ` Cornelia Huck
2017-09-21 11:00 ` Halil Pasic
2017-09-27 14:15 ` Halil Pasic
2017-09-28 15:19 ` Cornelia Huck
2017-09-28 15:20 ` Halil Pasic
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=8abd41f8-e3fd-682f-1669-a5c3870c32fd@linux.vnet.ibm.com \
--to=pasic@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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;
as well as URLs for NNTP newsgroup(s).