From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jasper Niebuhr <yjnworkstation@gmail.com>,
Willy Tarreau <w@1wt.eu>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] exitz syscall
Date: Sun, 12 Nov 2023 14:03:19 -0500 [thread overview]
Message-ID: <ZVEhd1ZbzBlawHz8@mit.edu> (raw)
In-Reply-To: <CAHk-=wj1qDhzGRYnfHb-jYHiT_3x+PuA8Zk9FosCzm5OL6e=GQ@mail.gmail.com>
On Sun, Nov 12, 2023 at 10:50:10AM -0800, Linus Torvalds wrote:
>
> However, it still needs to also make sure that the memory in question
> is not file-backed etc. Which the patch I saw didn't seem to do
> either.
Well, yes. If the program isn't using a small amount of anonymous
memory, which is also mlock'ed so it doesn't get written to swap, the
rest of it is a total waste of time.
And from what I've seen from the O_PONIES debate (e.g., users
truncating files and rewriting them, and then complaining when the
top-ten score file disappears after the system crashes when they close
the OpenGL connection to the proprietary kernel driver), my basic
assumption is that anything application writers will get wrong, they
probably will....
- Ted
next prev parent reply other threads:[~2023-11-12 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 12:51 [PATCH] exitz syscall York Jasper Niebuhr
2023-11-11 13:24 ` Willy Tarreau
2023-11-12 1:24 ` Linus Torvalds
2023-11-12 10:03 ` Jasper Niebuhr
2023-11-12 15:44 ` Theodore Ts'o
2023-11-12 18:50 ` Linus Torvalds
2023-11-12 19:03 ` Theodore Ts'o [this message]
2023-11-13 0:08 ` Andy Lutomirski
2023-11-12 4:52 ` Theodore Ts'o
2023-11-13 7:37 ` Vlastimil Babka
2023-11-19 14:54 ` Jasper Niebuhr
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=ZVEhd1ZbzBlawHz8@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
--cc=yjnworkstation@gmail.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;
as well as URLs for NNTP newsgroup(s).