all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, phst@google.com,
	Lars Ingebrigtsen <larsi@gnus.org>,
	p.stephani2@gmail.com, emacs-devel@gnu.org
Subject: Re: emacs-28 6d3608be88: Seccomp: improve support for newer versions of glibc (Bug#51073)
Date: Mon, 24 Jan 2022 17:47:19 +0100	[thread overview]
Message-ID: <87h79thyi0.fsf@gmail.com> (raw)
In-Reply-To: <83ilu9ji0m.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Jan 2022 17:00:25 +0200")

>>>>> On Mon, 24 Jan 2022 17:00:25 +0200, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Lars Ingebrigtsen <larsi@gnus.org>
    >> Date: Mon, 24 Jan 2022 15:38:24 +0100
    >> Cc: Po Lu <luangruo@yahoo.com>, phst@google.com, p.stephani2@gmail.com,
    >> emacs-devel@gnu.org
    >> 
    >> Eli Zaretskii <eliz@gnu.org> writes:
    >> 
    >> >> It apparently leads to crashes when Emacs is run under seccomp with a
    >> >> recent glibc version.
    >> >
    >> > That can happen any day, if glibc folks make some change we didn't
    >> > know about.  We cannot chase glibc development forever, we will never
    >> > succeed catching up with them, certainly not in the long run.
    >> 
    >> But this is a known glibc issue, and crashes aren't fun, so I think the
    >> seccomp change was warranted on the release branch.

    Eli> It is very worrisome that a change in glibc can break Emacs like that.
    Eli> I wonder what it means for the maintainability of Emacs in the long
    Eli> run.  I have a bad feeling about this.

We can always default the seccomp support to off.

Robert
-- 



  reply	other threads:[~2022-01-24 16:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164286838577.8429.4021499312049157333@vcs2.savannah.gnu.org>
     [not found] ` <20220122161946.44098C0DA30@vcs2.savannah.gnu.org>
2022-01-24  0:08   ` emacs-28 6d3608be88: Seccomp: improve support for newer versions of glibc (Bug#51073) Po Lu
2022-01-24 10:44     ` Philipp Stephani
2022-01-24 12:53       ` Eli Zaretskii
2022-01-24 13:33         ` Po Lu
2022-01-24 13:41           ` Eli Zaretskii
2022-01-24 14:38             ` Lars Ingebrigtsen
2022-01-24 15:00               ` Eli Zaretskii
2022-01-24 16:47                 ` Robert Pluim [this message]
2022-01-24 17:19                   ` Eli Zaretskii
2022-01-25 20:12                     ` Philipp Stephani
2022-01-26  3:23                       ` Eli Zaretskii
2022-01-25 20:09                 ` Philipp Stephani
2022-01-25 21:40                   ` Stefan Monnier
2022-01-26  3:22                   ` Eli Zaretskii
2022-01-25  4:16       ` Richard Stallman
2022-01-25 12:08         ` Eli Zaretskii
2022-01-25 20:13           ` Philipp Stephani
2022-01-26  3:24             ` Eli Zaretskii

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=87h79thyi0.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    --cc=p.stephani2@gmail.com \
    --cc=phst@google.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.