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=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS 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 E0A01C43381 for ; Mon, 11 Mar 2019 13:19:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B0BD920657 for ; Mon, 11 Mar 2019 13:19:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727436AbfCKNTH (ORCPT ); Mon, 11 Mar 2019 09:19:07 -0400 Received: from www262.sakura.ne.jp ([202.181.97.72]:17744 "EHLO www262.sakura.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726826AbfCKNTH (ORCPT ); Mon, 11 Mar 2019 09:19:07 -0400 Received: from fsav304.sakura.ne.jp (fsav304.sakura.ne.jp [153.120.85.135]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id x2BDImNr013962; Mon, 11 Mar 2019 22:18:48 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav304.sakura.ne.jp (F-Secure/fsigk_smtp/530/fsav304.sakura.ne.jp); Mon, 11 Mar 2019 22:18:48 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/530/fsav304.sakura.ne.jp) Received: from [192.168.1.8] (softbank126126163036.bbtec.net [126.126.163.36]) (authenticated bits=0) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTPSA id x2BDIh6F013947 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NO); Mon, 11 Mar 2019 22:18:47 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Subject: Re: [PATCH] tomoyo: Add a kernel config option for fuzzing testing. To: James Morris Cc: Stephen Smalley , linux-security-module@vger.kernel.org References: <19e3dbac-d3ac-53b2-6e98-faf927bc72b3@i-love.sakura.ne.jp> <05b05166-d24a-3c50-6556-472f50a239b9@tycho.nsa.gov> <201903042359.x24NxJwx065719@www262.sakura.ne.jp> From: Tetsuo Handa Message-ID: <72b3b8e1-fc34-f312-de12-cf42992bceb8@i-love.sakura.ne.jp> Date: Mon, 11 Mar 2019 22:18:40 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-security-module@vger.kernel.org Precedence: bulk List-ID: On 2019/03/05 12:32, James Morris wrote: > On Tue, 5 Mar 2019, Tetsuo Handa wrote: > >> I guess that majority of TOMOYO users are now using the upstream version. But >> pre-LSM version and/or AKARI will remain there until LKM-based LSMs becomes >> officially supported > > You mean dynamically loadable LSMs? Yes. As long as upstream can't accept all LSM modules, and some people cannot afford utilizing upstream LSM modules, LKM-based LSMs will be needed by such people. > > There are no plans to support this. Currently you don't have a plan. But I have. It took 10+ years to be able to allow coexisting inode based access control and name based access control. And there are people who still cannot afford keeping upstream LSM modules enabled. Anyway, your question is irrelevant to whether to allow syzbot to test TOMOYO module. syzbot already bisected this problem to an innocent commit 89a9684ea158dd7e ("LSM: Ignore "security=" when "lsm=" is specified") at https://syzkaller.appspot.com/bug?id=32ab41bbdc0c28643c507dd0cf1eea1a9ce67837 . Will you send this patch to linux.git so that syzbot can test TOMOYO module?