From: "Torsten Bögershausen" <tboegi@web.de>
To: rsbecker@nexbridge.com
Cc: git@vger.kernel.org
Subject: Re: [BUG] 2.44.0 t7704.9 Fails on NonStop ia64
Date: Sun, 25 Feb 2024 20:19:54 +0100 [thread overview]
Message-ID: <20240225191954.GA28646@tb-raspi4> (raw)
In-Reply-To: <01be01da681e$0c349090$249db1b0$@nexbridge.com>
On Sun, Feb 25, 2024 at 02:08:35PM -0500, rsbecker@nexbridge.com wrote:
> On Sunday, February 25, 2024 1:45 PM, I wrote:
> >To: git@vger.kernel.org
> >Subject: [BUG] 2.44.0 t7704.9 Fails on NonStop ia64
> >
> >This appears to be a new issue introduced at 2.44.0. It only occurs on
> NonStop ia64
> >1..9
[snip]
>
> I did find the following calls to write(), one of which might be involved.
> write() should not be used directly unless the count is clearly very small.
> Xwrite() should be used instead. There are other calls but those are either
> small or not on platform.
(Probably a typ0: Xwrite() -> xwrite()
But I think that this should be used:
write_in_full()
>
> reftable/writer.c: int n = w->write(w->write_arg, zeroed,
> w->pending_padding);
> reftable/writer.c: n = w->write(w->write_arg, data, len);
> run-command.c: len = write(io->fd, io->u.out.buf,
> t/helper/test-path-utils.c: if (write(1, buffer, count)
> < 0)
> t/helper/test-windows-named-pipe.c: write(1, buf, nbr);
> t/helper/test-windows-named-pipe.c: write(1, buf, nbr);
> trace2/tr2_dst.c: bytes = write(fd, buf_line->buf, buf_line->len);
>
>
>
>
next prev parent reply other threads:[~2024-02-25 19:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 18:44 [BUG] 2.44.0 t7704.9 Fails on NonStop ia64 rsbecker
2024-02-25 19:08 ` rsbecker
2024-02-25 19:19 ` Torsten Bögershausen [this message]
2024-02-25 20:36 ` rsbecker
2024-02-26 15:32 ` Phillip Wood
2024-02-26 15:52 ` rsbecker
2024-02-26 16:00 ` Phillip Wood
2024-02-26 18:03 ` rsbecker
2024-02-26 19:02 ` rsbecker
2024-02-26 19:45 ` phillip.wood123
2024-02-27 8:45 ` Patrick Steinhardt
2024-02-27 10:43 ` phillip.wood123
2024-02-27 14:10 ` rsbecker
2024-02-27 14:22 ` Patrick Steinhardt
2024-02-27 14:28 ` rsbecker
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=20240225191954.GA28646@tb-raspi4 \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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 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.