From: <rsbecker@nexbridge.com>
To: "'Patrick Steinhardt'" <ps@pks.im>, <phillip.wood@dunelm.org.uk>
Cc: "'Torsten Bögershausen'" <tboegi@web.de>, git@vger.kernel.org
Subject: RE: [BUG] 2.44.0 t7704.9 Fails on NonStop ia64
Date: Tue, 27 Feb 2024 09:10:55 -0500 [thread overview]
Message-ID: <02c501da6986$cb7c5c30$62751490$@nexbridge.com> (raw)
In-Reply-To: <Zd2hMmIzHKQ7JE45@tanuki>
On Tuesday, February 27, 2024 3:46 AM, Patrick Steinhardt wrote:
>On Mon, Feb 26, 2024 at 03:32:14PM +0000, Phillip Wood wrote:
>> Hi Randal
>>
>> [cc'ing Patrick for the reftable writer]
>>
>> > The question is which call is bad? The cruft stuff is relatively new
>> > and I don't know the code.
>> >
>> > > > 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);
>>
>> Neither of these appear to check for short writes and
>> reftable_fd_write() is a thin wrapper around write(). Maybe
>> reftable_fd_write() should be using write_in_full()?
>
>It already does starting with 85a8c899ce (reftable: handle interrupted
writes, 2023-12-11):
>
>```
>static ssize_t reftable_fd_write(void *arg, const void *data, size_t sz) {
> int *fdp = (int *)arg;
> return write_in_full(*fdp, data, sz);
>}
Unfortunately, this fix is included in what I am testing but does not impact
the issue I am seeing one way or another, but thank you.
next prev parent reply other threads:[~2024-02-27 14:11 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
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 [this message]
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='02c501da6986$cb7c5c30$62751490$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
--cc=tboegi@web.de \
/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).