From mboxrd@z Thu Jan 1 00:00:00 1970 From: oleg@redhat.com (Oleg Nesterov) Date: Fri, 27 Jun 2014 21:27:53 +0200 Subject: [PATCH v8 5/9] seccomp: split mode set routines In-Reply-To: References: <20140625173245.GA17695@redhat.com> <20140625175136.GA18185@redhat.com> Message-ID: <20140627192753.GA30752@redhat.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 06/27, Kees Cook wrote: > > It looks like SMP ARM issues dsb for rmb, which seems a bit expensive. > http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0204g/CIHJFGFE.htm > > ... > > I really want to avoid adding anything to the secure_computing() > execution path. :( I must have missed something but I do not understand your concerns. __secure_computing() is not trivial, and we are going to execute the filters. Do you really think rmb() can add the noticeable difference? Not to mention that we can only get here if we take the slow syscall enter path due to TIF_SECCOMP... Oleg.