From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Albert Cahalan" Subject: Re: [PATCH 0/2] LogFS take two Date: Tue, 8 May 2007 01:53:38 -0400 Message-ID: <787b0d920705072253vd9eb7c4o893412d28706c9a6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: joern@lazybastard.org, akpm@osdl.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, shaggy@linux.vnet.ibm.com, dgc@sgi.com Return-path: Received: from wr-out-0506.google.com ([64.233.184.234]:2929 "EHLO wr-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755286AbXEHFyI (ORCPT ); Tue, 8 May 2007 01:54:08 -0400 Received: by wr-out-0506.google.com with SMTP id 76so1856187wra for ; Mon, 07 May 2007 22:54:07 -0700 (PDT) Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org joern@lazybastard.org, akpm@osdl.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, shaggy@linux.vnet.ibm.com, dgc@sgi.com Re: [PATCH 0/2] LogFS take two You seem to be missing the immutable bit. This is really useful for dealing with buggy or badly-designed things running as root. I've used to to protect /dev/null from becoming a normal file filled with junk, and to protect /etc/resolv.conf from "helpful" network management daemons that don't know my DNS servers. Anything else missing? BTW, BSD offers an unprivileged immutable bit as well. I'm sure it's useful for the apps that trash their own config files. Actually, this bit alone would do fine, and we could really use a way to protect writable device files from deletion or permission bit changes.