All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: phillip.wood@dunelm.org.uk
Cc: rsbecker@nexbridge.com, "'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:45:38 +0100	[thread overview]
Message-ID: <Zd2hMmIzHKQ7JE45@tanuki> (raw)
In-Reply-To: <5e807c1c-20a0-407b-9fc2-acd38521ba45@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

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);
}
```

Patrick

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2024-02-27  8:45 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 [this message]
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=Zd2hMmIzHKQ7JE45@tanuki \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=rsbecker@nexbridge.com \
    --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 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.