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 X-Spam-Level: X-Spam-Status: No, score=-19.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1, USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9F6AFC433E0 for ; Tue, 12 Jan 2021 00:56:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6B0BA225AB for ; Tue, 12 Jan 2021 00:56:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727888AbhALA4w (ORCPT ); Mon, 11 Jan 2021 19:56:52 -0500 Received: from linux.microsoft.com ([13.77.154.182]:47184 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727261AbhALA4v (ORCPT ); Mon, 11 Jan 2021 19:56:51 -0500 Received: from [192.168.1.2] (unknown [67.183.157.164]) by linux.microsoft.com (Postfix) with ESMTPSA id F073F20B6C40 for ; Mon, 11 Jan 2021 16:56:10 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com F073F20B6C40 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1610412971; bh=eFeujejIXY4wfwMx5x9iUp5aKt0caZQO/QFQMuBSg0g=; h=To:From:Subject:Date:From; b=QtZFOR11EZzKDMe550iTSfmi7NbIjd8hUiKBTG5whGLJ3zEc4gwqNYa7L6tHCoE2m UfsqvDzWAtvkvZF35UxCm8rWmto5ldR3wMbC5VFJ0n8l6ZAcMaBVPJtzevvuxqy9WK 8pgfnHr2Nf3IjtXj/ThANSj7/ZYjr0o93XRlvJgw= To: linux-security-module@vger.kernel.org From: Fan Wu Subject: Question about inode security blob Message-ID: <156f6860-73a4-f754-b460-d64de40ff626@linux.microsoft.com> Date: Mon, 11 Jan 2021 16:56:09 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: Hi, I'm trying to learn the security blob infrastructure for my future LSM development. Unlike other blobs, I found inode security blob has a special pattern. I couldn’t find useful information on the web so I think this mail list is the most appropriate place to ask this question. The BPF and SELinux will check whether the inode->i_security is NULL before use https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/include/linux/bpf_lsm.h#n35 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/security/selinux/include/objsec.h#n164 But for smack, it doesn't do such a check https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/security/smack/smack.h#n347 Is this because smack_set_mnt_opts() already does the NULL check at https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/security/smack/smack_lsm.c#n784 ? Also, I wonder in which situation will the inode->i_security be NULL? Thanks, and I hope I could make my contributions to LSM soon. Best, Fan