From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] destroy unused shmem segments
Date: Mon, 13 Jun 2011 11:07:00 +0400 [thread overview]
Message-ID: <20110613070700.GA22659@openwall.com> (raw)
In-Reply-To: <20110613064252.GB3877@albatros>
Vasiliy,
On Mon, Jun 13, 2011 at 10:42:52AM +0400, Vasiliy Kulikov wrote:
> Is it some additional "safety" check or a workaround for some dubious
> race?
Neither. IIRC, I thought that this was needed, and not as a workaround,
nor because of a race. However, your analysis appears to be correct to
me. This leaves us with the following three possibilities:
- The extra code was never needed. This is unlikely because I was
adding those pieces of code based on my testing results.
- The extra code was needed for some older kernel version (maybe older
than 2.4), then forward-ported (not carefully enough to spot this).
(Most CONFIG_HARDEN_* features 2.4.x-ow date back to my patches for 2.0.)
- We're missing something now.
I think that you don't need to figure out which it is. Rather, you
need to implement the functionality for 3.0 and test it. Then do it for
RHEL6/OpenVZ as well.
> I see no explicit need of such freeing cycle in do_exit().
Yes, it appears so from your analysis.
Thanks,
Alexander
next prev parent reply other threads:[~2011-06-13 7:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 6:42 [kernel-hardening] destroy unused shmem segments Vasiliy Kulikov
2011-06-13 7:07 ` Solar Designer [this message]
2011-06-14 8:33 ` Vasiliy Kulikov
2011-06-15 14:42 ` Solar Designer
-- strict thread matches above, loose matches on Subject: below --
2011-06-14 17:51 Vasiliy Kulikov
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=20110613070700.GA22659@openwall.com \
--to=solar@openwall.com \
--cc=kernel-hardening@lists.openwall.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