From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/file: bump to version 5.48
Date: Wed, 4 Nov 2026 22:24:41 +0100 [thread overview]
Message-ID: <auuiaUH0JJ20VZWV@windsurf> (raw)
In-Reply-To: <20261103064034.3913314-1-yegorslists@googlemail.com>
On Tue, Nov 03, 2026 at 07:40:34AM +0100, Yegor Yefremov via buildroot wrote:
> https://github.com/file/file/blob/FILE5_48/ChangeLog
>
> 5.48 adds Landlock sandboxing, which is enabled when the toolchain
> provides linux/landlock.h and skipped at runtime on kernels without
> Landlock support.
>
> Add two patches fixing the seccomp build, broken by the new syscall
> rules in 5.48:
>
> - with musl, where pread64 is a macro once seccomp.c includes
> <unistd.h>;
> - with kernel headers older than 5.9, which lack openat2, faccessat2
> or close_range.
>
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Applied to master, thanks!
I continue to be amazed that key open-software like file has a website
like this: https://astron.com/, no Git repository, no mailing list, no
nothing...
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-11-04 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 6:40 [Buildroot] [PATCH] package/file: bump to version 5.48 Yegor Yefremov via buildroot
2026-11-04 21:24 ` Thomas Petazzoni via buildroot [this message]
2026-11-04 22:19 ` Yegor Yefremov via buildroot
2026-11-04 22:44 ` Thomas Petazzoni via buildroot
2026-11-04 23:08 ` Yegor Yefremov via buildroot
2026-11-05 7:39 ` Thomas Petazzoni via buildroot
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=auuiaUH0JJ20VZWV@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yegorslists@googlemail.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