From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4660AC28CF5 for ; Wed, 26 Jan 2022 09:16:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238924AbiAZJQw (ORCPT ); Wed, 26 Jan 2022 04:16:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40990 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231514AbiAZJQv (ORCPT ); Wed, 26 Jan 2022 04:16:51 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 507F0C06161C; Wed, 26 Jan 2022 01:16:51 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id E1208615C4; Wed, 26 Jan 2022 09:16:50 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6FE54C340E3; Wed, 26 Jan 2022 09:16:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1643188610; bh=WdvfffKVI6ApzghM8ddJv7JS3Pdt2YGhtMfAC6gP/Po=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=TKr7Zjubut89IiBL5pcdAuYfHLDnWKNOVwZxV2W+EVfYcW0S7WJGrOiRLxEr7mzmv Qrq+CIpuKOXvIzchykg7MWLi1BfhIri9HC4A/X8NzyIlBpkmuSOkclOt2RMuQb5OLN RcVnTPaSTZGwoJ1CYG3d+k5CllfGBLZdJ1/dNTTDfis0JO143wdtMMfmFgDan4yFpt sfd0cw1F3CqhItiJ4IiBbopGrHVUgSSEHJ2fBUK8w4QROQxGWEVVMDhjC6BGA9+Yd/ sgoFPHcruwh+VwmS1KJVALFloyHu/pDPPrmA5A0wVOVunvogy+Z8X+uYZKQQa/Oymy h09DWowN89euQ== Date: Wed, 26 Jan 2022 10:16:42 +0100 From: Christian Brauner To: Stefan Berger Cc: linux-integrity@vger.kernel.org, zohar@linux.ibm.com, serge@hallyn.com, christian.brauner@ubuntu.com, containers@lists.linux.dev, dmitry.kasatkin@gmail.com, ebiederm@xmission.com, krzysztof.struczynski@huawei.com, roberto.sassu@huawei.com, mpeters@redhat.com, lhinds@redhat.com, lsturman@redhat.com, puiterwi@redhat.com, jejb@linux.ibm.com, jamjoom@us.ibm.com, linux-kernel@vger.kernel.org, paul@paul-moore.com, rgb@redhat.com, linux-security-module@vger.kernel.org, jmorris@namei.org, Stefan Berger Subject: Re: [PATCH v9 07/23] ima: Move ima_htable into ima_namespace Message-ID: <20220126091642.3gvrlgx7767xvmho@wittgenstein> References: <20220125224645.79319-1-stefanb@linux.vnet.ibm.com> <20220125224645.79319-8-stefanb@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20220125224645.79319-8-stefanb@linux.vnet.ibm.com> Precedence: bulk List-ID: On Tue, Jan 25, 2022 at 05:46:29PM -0500, Stefan Berger wrote: > From: Stefan Berger > > Move ima_htable into ima_namespace. This way a front-end like > securityfs can show the number of violations of an IMA namespace. > > Signed-off-by: Stefan Berger > --- Moving into imans looks good, Acked-by: Christian Brauner