From: Kees Cook <keescook@chromium.org>
To: Steve Langasek <steve.langasek@canonical.com>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH] Always build for LFS mode on 32-bit archs.
Date: Sat, 17 Feb 2024 13:54:14 -0800 [thread overview]
Message-ID: <202402171351.439742DA@keescook> (raw)
In-Reply-To: <Zc6tzKPsYZRICHya@homer.dodds.net>
On Thu, Feb 15, 2024 at 04:35:24PM -0800, Steve Langasek wrote:
> index a0948853..78953870 100644
> --- a/libselinux/include/selinux/selinux.h
> +++ b/libselinux/include/selinux/selinux.h
> @@ -1,6 +1,7 @@
> #ifndef _SELINUX_H_
> #define _SELINUX_H_
>
> +#include <stdint.h>
> #include <sys/types.h>
> #include <stdarg.h>
>
> @@ -521,7 +522,11 @@ extern int matchpathcon_index(const char *path,
> with the same inode (e.g. due to multiple hard links). If so, then
> use the latter of the two specifications based on their order in the
> file contexts configuration. Return the used specification index. */
> -extern int matchpathcon_filespec_add(ino_t ino, int specind, const char *file);
> +typedef uint64_t libselinux_ino_t;
> +#if _FILE_OFFSET_BITS == 64 && __BITS_PER_LONG < 64
> +#define matchpathcon_filespec_add matchpathcon_filespec_add64
> +#endif
> +extern int matchpathcon_filespec_add(libselinux_ino_t ino, int specind, const char *file);
What's the ABI goal here? I think the type is wrong -- doesn't this need
to be uint32_t not a uint64_t for the wrapper?
--
Kees Cook
next prev parent reply other threads:[~2024-02-17 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 0:32 [PATCH] Always build for LFS mode on 32-bit archs Steve Langasek
2024-02-16 0:35 ` Steve Langasek
2024-02-17 21:54 ` Kees Cook [this message]
2024-02-18 3:08 ` Steve Langasek
2024-02-25 6:45 ` Steve Langasek
2024-02-26 17:52 ` Christian Göttsche
2024-02-27 7:00 ` Steve Langasek
2024-02-27 17:13 ` Christian Göttsche
2024-02-28 6:11 ` Steve Langasek
2024-02-28 9:20 ` Petr Lautrbach
2024-03-03 8:00 ` Steve Langasek
2024-06-02 16:40 ` Chris Hofstaedtler
-- strict thread matches above, loose matches on Subject: below --
2024-11-28 16:54 Christian Göttsche
2024-12-16 21:26 ` James Carter
2024-12-17 20:25 ` James Carter
2024-02-16 0:18 Steve Langasek
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=202402171351.439742DA@keescook \
--to=keescook@chromium.org \
--cc=selinux@vger.kernel.org \
--cc=steve.langasek@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox