Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756139Ab0LIMqw (ORCPT ); Thu, 9 Dec 2010 07:46:52 -0500 Received: from mx1.vsecurity.com ([209.67.252.12]:60614 "EHLO mx1.vsecurity.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755305Ab0LIMqv (ORCPT ); Thu, 9 Dec 2010 07:46:51 -0500 Subject: Re: [PATCH] kptr_restrict for hiding kernel pointers from unprivileged users From: Dan Rosenberg To: Eric Dumazet Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, netdev In-Reply-To: <1291895472.2965.4.camel@Dan> References: <1291863926.2965.1.camel@Dan> <1291865039.2795.46.camel@edumazet-laptop> <1291895472.2965.4.camel@Dan> Content-Type: text/plain; charset="UTF-8" Date: Thu, 09 Dec 2010 07:46:41 -0500 Message-ID: <1291898801.2965.6.camel@Dan> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 604 Lines: 26 > > So caller can not block BH ? > > > > This seems wrong to me, please consider : > > > > normal process context : > > > > spin_lock_bh() ... > > > > for (...) > > {xxx}printf( ... "%pK" ...) > > > > spin_unlock_bh(); > > > > I will think about this and address it. Would you be happier if I omitted the in_interrupt() check entirely? -Dan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/