qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
	"Thomas Huth" <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	qemu-stable@nongnu.org
Subject: Re: [PATCH v2 5/9] chardev/char-pty: Do not ignore chr_write() failures
Date: Wed, 12 Nov 2025 13:51:18 +0100	[thread overview]
Message-ID: <a735e5ce-b846-4f50-b98e-68457b1fb616@linaro.org> (raw)
In-Reply-To: <CAJ+F1CJ4xxh-y_S89gG86gfEdEYviQ=ajvcC8OW4a8XfFW2gLg@mail.gmail.com>

On 28/10/25 14:44, Marc-André Lureau wrote:
> Hi
> 
> On Wed, Oct 22, 2025 at 7:09 PM Philippe Mathieu-Daudé
> <philmd@linaro.org> wrote:
>>
>> Cc: qemu-stable@nongnu.org
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> ---
>> If ignoring this is deliberate, this must be described in a comment
>> to avoid any confusion.
> 
> Agree
> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>

Thanks!

> 
> This is from commit 4f7689f08 ("chardev/char-pty: Avoid losing bytes
> when the other side just (re-)connected")
> 
> note: It's mildly annoying that the pty backend has still
> !s->connected and we are writing.

Per the comment, "already re-connected, but timer not fired yet".

> I wonder why the frontend is not
> respecting the backend opened state, probably some race or buffering.

Do you mind opening an issue? I'm not familiar with this code.

> 
> 
>> ---
>>   chardev/char-pty.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/chardev/char-pty.c b/chardev/char-pty.c
>> index b066f014126..652b0bd9e73 100644
>> --- a/chardev/char-pty.c
>> +++ b/chardev/char-pty.c
>> @@ -125,7 +125,7 @@ static int char_pty_chr_write(Chardev *chr, const uint8_t *buf, int len)
>>       rc = RETRY_ON_EINTR(g_poll(&pfd, 1, 0));
>>       g_assert(rc >= 0);
>>       if (!(pfd.revents & G_IO_HUP) && (pfd.revents & G_IO_OUT)) {
>> -        io_channel_send(s->ioc, buf, len);
>> +        return io_channel_send(s->ioc, buf, len);
>>       }
>>
>>       return len;
>> --
>> 2.51.0
>>
>>
> 
> 



  reply	other threads:[~2025-11-12 13:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 15:07 [PATCH v2 0/9] chardev: Improve @docstring and clarify qemu_chr_write() uses Philippe Mathieu-Daudé
2025-10-22 15:07 ` [PATCH v2 1/9] chardev/char-fe: Improve @docstrings Philippe Mathieu-Daudé
2025-10-22 15:07 ` [PATCH v2 2/9] chardev/char-io: Add @docstrings for io_channel_send[_full]() Philippe Mathieu-Daudé
2025-10-22 15:07 ` [PATCH v2 3/9] chardev/char: Improve ChardevClass::chr_write() docstring Philippe Mathieu-Daudé
2025-10-28 13:30   ` Marc-André Lureau
2025-10-22 15:07 ` [PATCH v2 4/9] chardev/char: Document qemu_chr_write[_all]() Philippe Mathieu-Daudé
2025-10-28 13:32   ` Marc-André Lureau
2025-10-22 15:07 ` [PATCH v2 5/9] chardev/char-pty: Do not ignore chr_write() failures Philippe Mathieu-Daudé
2025-10-28 13:44   ` Marc-André Lureau
2025-11-12 12:51     ` Philippe Mathieu-Daudé [this message]
2025-10-22 15:07 ` [PATCH v2 6/9] chardev/char: Allow partial writes in qemu_chr_write() Philippe Mathieu-Daudé
2025-10-28 13:53   ` Marc-André Lureau
2025-10-22 15:07 ` [PATCH v2 7/9] chardev/char: Preserve %errno " Philippe Mathieu-Daudé
2025-10-22 15:14   ` Philippe Mathieu-Daudé
2025-10-28 14:25     ` Peter Maydell
2025-11-12  8:33       ` Philippe Mathieu-Daudé
2025-10-28 14:00   ` Marc-André Lureau
2025-10-28 14:19     ` Daniel P. Berrangé
2025-10-22 15:07 ` [PATCH v2 8/9] chardev/char-hub: Retry when qemu_chr_fe_write() can not write Philippe Mathieu-Daudé
2025-10-28 14:04   ` Marc-André Lureau
2025-10-22 15:07 ` [PATCH v2 9/9] hw/char: Simplify when qemu_chr_fe_write() could " Philippe Mathieu-Daudé
2025-10-28 14:07   ` Marc-André Lureau
2025-10-22 15:16 ` [PATCH v2 0/9] chardev: Improve @docstring and clarify qemu_chr_write() uses Philippe Mathieu-Daudé

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=a735e5ce-b846-4f50-b98e-68457b1fb616@linaro.org \
    --to=philmd@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=marcandre.lureau@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).