12
KDE Neon using tmpfs for /tmp seems like an horrible idea?
(lemmy.kde.social)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Apr 2024
12 points (83.3% liked)
KDE
5391 readers
158 users here now
KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
Plasma 6 Bugs
If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
founded 1 year ago
MODERATORS
I think, and i'm open to alternative theories, is that using RAM instead of disk is safer when the tmp directory fills up.
If you have /tmp being a regular directory on your root drive, if you fill your disk witg tmp files, other processes wont be able to save files to disk, resulting in lost data.
If you have it in a ram disk, when the tmpfs fills up too much, the oom killer can get more space (unsure if oomkiller can wipe tmpfs, but that probably would be ideal?).
Neither are good, and both can result in data loss, but tmpfs may be safer?
wouldn't that open up additional vulnerabilities?
Are you thinking rowhammer? My understanding is limited, but doesnt rowhammer require being able to write to memory at a consistent address, co-located with the data being attacked? Im not sure thats doable with tmpfs, but probably worth an investigation by someone more knowledgable than me :)