From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Why replacing running executable file is forbidden, but overwriting of memory mapped shared object is allowed ?
Date: Fri, 10 Nov 2017 14:04:41 -0500 [thread overview]
Message-ID: <31575.1510340681@turing-police.cc.vt.edu> (raw)
In-Reply-To: <489841510337062@web43g.yandex.ru>
On Fri, 10 Nov 2017 21:04:22 +0300, Lev Olshvang said:
> I am going to patch inode reference count of mapped shared libs
Congrats. You just corrupted your file system.
Hint 1: What happens if you decrement the count by one unnecessarily,
and later on, probably during system shutdown, the reference count drops
to zero instead of one?
Hint 2: What happens if you incremented the count, and at system shutdown,
there's still a reference left when the kernel tries to unmount and sync the
filesystem?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20171110/a7855194/attachment.bin
next prev parent reply other threads:[~2017-11-10 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 13:30 Why replacing running executable file is forbidden, but overwriting of memory mapped shared object is allowed ? Lev Olshvang
2017-11-10 14:52 ` Ricardo Ribalda Delgado
2017-11-10 16:24 ` valdis.kletnieks at vt.edu
2017-11-10 18:04 ` Lev Olshvang
2017-11-10 19:04 ` valdis.kletnieks at vt.edu [this message]
2017-11-14 11:18 ` Lev Olshvang
2017-11-14 16:59 ` valdis.kletnieks at vt.edu
2017-11-10 17:49 ` Jeffrey Walton
2017-11-10 22:43 ` Ruben Safir
2017-11-11 0:05 ` valdis.kletnieks at vt.edu
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=31575.1510340681@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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 NNTP newsgroup(s).