All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai <xenomai@lists.linux.dev>
Subject: Re: [PATCH] Add build time guard to detect off_t mismatch
Date: Thu, 7 May 2026 16:10:04 +0200 (CEST)	[thread overview]
Message-ID: <472857942.3063.1778163004494.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <84f6c3a9-b764-4774-b048-eb8e0c7fdc99@siemens.com>

----- Ursprüngliche Mail -----
> Von: "Jan Kiszka" <jan.kiszka@siemens.com>
>> Ah, sorry for not being clear.
>> Your fix is in next and not part of a release, and the application in
>> question uses Xenomai 3.2.6...
> 
> But 3.2.x is not affected by the mmap off_t issue?! Still confused.

Well, the issue I'm talking about was a build issue.
Xenomai was configured without _FILE_OFFSET_BITS=64, but the application was with.
Not Xenomai's fault, of course.

But when the application started to use mmap() the off_t used in the application
had 8 bytes, but Xenomai expected 4. So, the mmap() offset parameter was wrong.

Thanks,
//richard

  reply	other threads:[~2026-05-07 14:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 12:23 [PATCH] Add build time guard to detect off_t mismatch Richard Weinberger
2026-05-07 12:26 ` Jan Kiszka
2026-05-07 12:32   ` Richard Weinberger
2026-05-07 12:54     ` Jan Kiszka
2026-05-07 12:55       ` Richard Weinberger
2026-05-07 14:02         ` Jan Kiszka
2026-05-07 14:10           ` Richard Weinberger [this message]
2026-05-07 14:16             ` Jan Kiszka
2026-05-07 14:26               ` Richard Weinberger
2026-05-12 13:01               ` Richard Weinberger
2026-05-12 13:08                 ` Jan Kiszka
2026-05-12 13:15                   ` Richard Weinberger
2026-05-12 14:26                     ` Florian Bezdeka
2026-05-12 15:04                       ` Richard Weinberger
2026-05-12 15:27                         ` Florian Bezdeka

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=472857942.3063.1778163004494.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@lists.linux.dev \
    /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.