public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org, dave.anglin@bell.net, fweimer@redhat.com
Subject: Re: [PATCH v2] hppa: Drop old parisc-specific MADV_* constants
Date: Sat, 11 Feb 2023 07:37:49 +0100	[thread overview]
Message-ID: <595f5482-c55a-275c-3729-1e1f0af7719a@gmx.de> (raw)
In-Reply-To: <ed8a3b74-1eff-1411-98c9-bf7781dd8473@codesourcery.com>

On 2/10/23 22:48, Joseph Myers wrote:
> On Fri, 10 Feb 2023, Helge Deller via Libc-alpha wrote:
>
>> -  [Add deprecations, removals and changes affecting compatibility here]
>> +* In the Linux kernel for the hppa/parisc architecture some of the
>> +  MADV_XXX constants were changed to have the same values as the other
>> +  architectures.  New programs compiled with this glibc version and which
>> +  use the madvise call will require at least Linux kernel version 6.2,
>> +  alternatively stable kernels from versions 6.1.6, 5.15.87, 5.10.163,
>> +  5.4.228, 4.19.270 or 4.14.303.
>
> Normally we'd be a lot more conservative about kernel version
> requirements, but if we require a new kernel we'd put it in
> arch_minimum_kernel in the relevant configure.ac.

Basically, programs compiled with the new MADV values should work even
on all older kernels since it's just an advise for the kernel which it may
ignore and for which programs should allow the syscall to fail.
The only program I've found so far to be more strict is the
tor-browser, which refuses to start if MADV_WIPEONFORK fails.
But it's unlikely people will use tor on parisc, and IMHO
if you care about security you should use a more recent kernel anyway.

That said, I can add arch_minimum_kernel=4.14.303 (or 6.2?) but I don't
think it's necessary.

Helge

  reply	other threads:[~2023-02-11  6:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 13:28 Helge Deller
2023-02-10 21:48 ` Joseph Myers
2023-02-11  6:37   ` Helge Deller [this message]
2023-02-11 15:56     ` John David Anglin
2023-02-22 15:35 ` Joseph Myers
2023-02-25 20:09   ` Helge Deller

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=595f5482-c55a-275c-3729-1e1f0af7719a@gmx.de \
    --to=deller@gmx.de \
    --cc=dave.anglin@bell.net \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).