public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: David Laight <david.laight.linux@gmail.com>,
	Daniel Palmer <daniel@thingy.jp>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] tools/nolibc: also handle _llseek system call
Date: Sun, 19 Apr 2026 18:10:07 +0200	[thread overview]
Message-ID: <aeT-X2b-XDppAvSN@1wt.eu> (raw)
In-Reply-To: <f8f2c630-6e97-47f2-8547-e87ecfe8e41a@t-8ch.de>

On Sun, Apr 19, 2026 at 05:38:26PM +0200, Thomas Weißschuh wrote:
> The "preference" the commit message is talking about is not the
> ifdeffery as quoted above. Rather it is in the *outer* ifdeffery.
> 
> > The commit message should rather say something like:
> > 
> >   On some architectures the llseek system call contains a leading
> >   underscore. Fall back to it when llseek is not available and use it
> >   for the lseek system call as it is necessary for 64-bit offset handling.
> 
> The preference is llseek > _llseek > lseek. The important bit is not
> the order of llseek vs _llseek, as these will never occurr together
> anyways, but that _llseek is preferred over lseek.
> 
> What about:
> 
>   On some architectures the llseek system call contains a leading
>   underscore. Treat it the same way as llseek and prefer it over the
>   plain lseek system call as is necessary for 64-bit offset handling.

Got it now! That's indeed clearer and I initially misunderstood it as
what you debunked above :-)

Thanks!
Willy

  reply	other threads:[~2026-04-19 16:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-18 10:19 [PATCH 0/7] tools/nolibc: large file support Thomas Weißschuh
2026-04-18 10:19 ` [PATCH 1/7] tools/nolibc: also handle _llseek system call Thomas Weißschuh
2026-04-18 11:23   ` David Laight
2026-04-18 11:56     ` Thomas Weißschuh
2026-04-18 16:03       ` David Laight
2026-04-19 15:22         ` Willy Tarreau
2026-04-19 15:38           ` Thomas Weißschuh
2026-04-19 16:10             ` Willy Tarreau [this message]
2026-04-18 10:19 ` [PATCH 2/7] tools/nolibc: add __nolibc_arg_to_reg() Thomas Weißschuh
2026-04-18 10:19 ` [PATCH 3/7] tools/nolibc: cast pointers returned from system calls through integers Thomas Weißschuh
2026-04-18 10:19 ` [PATCH 4/7] tools/nolibc: handle 64-bit system call arguments on x32 Thomas Weißschuh
2026-04-18 10:20 ` [PATCH 5/7] tools/nolibc: handle 64-bit system call arguments on MIPS N32 Thomas Weißschuh
2026-04-18 11:14   ` David Laight
2026-04-18 11:54     ` Thomas Weißschuh
2026-04-18 16:32       ` David Laight
2026-04-19 15:30       ` Willy Tarreau
2026-04-19 21:35         ` David Laight
2026-04-20 15:58           ` Thomas Weißschuh
2026-04-18 10:20 ` [PATCH 6/7] tools/nolibc: open files with O_LARGEFILE Thomas Weißschuh
2026-04-18 10:20 ` [PATCH 7/7] selftests/nolibc: test large file support Thomas Weißschuh
2026-04-18 14:01 ` [PATCH 0/7] tools/nolibc: " Daniel Palmer
2026-04-19 15:31 ` Willy Tarreau

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=aeT-X2b-XDppAvSN@1wt.eu \
    --to=w@1wt.eu \
    --cc=daniel@thingy.jp \
    --cc=david.laight.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.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