public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Rob MacKinnon <c4blem0nkey@gmail.com>
Cc: rob.mackinnon@gmail.com, Andreas Gruenbacher <agruen@suse.de>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	hpa@zytor.com, hugh@veritas.com, linux-kernel@vger.kernel.org
Subject: Re: tmpfs support of xattrs?
Date: Wed, 29 Oct 2008 09:12:35 -0700	[thread overview]
Message-ID: <49088B73.2080208@schaufler-ca.com> (raw)
In-Reply-To: <49088797.3060802@gmail.com>

Rob MacKinnon wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Casey Schaufler wrote:
>   
>> Rob MacKinnon wrote:
>>     
>>> Andreas Gruenbacher wrote:
>>>  
>>>       
>>>> On Monday, 27 October 2008 21:25:31 Stephen Smalley wrote:
>>>>    
>>>>         
>>>>> Looks like a bug in Smack's implementation of the inode_listsecurity
>>>>> hook to me.  Did you mean to enable Smack in your kernel config?
>>>>>       
>>>>>           
>>>> Yes, there is at least one bug there; this kernel is broken. You may
>>>> want to try booting with a kernel command line option like
>>>> "security=none", which *should* turn smack off.
>>>>
>>>> Andreas
>>>>     
>>>>         
>>> All,
>>>
>>> Indeed the kernel cmdline option security=none did disable smack. So
>>> atleast that works. Thank you all for helping me track this down.  I can
>>> now return to updating packages (some of which have been waiting
>>> patiently for this to be cleared up)!  Though I will be looking forward
>>> to this feature working as it was intended. ;)  Let me know if there is
>>> a bug # assigned and I'll quietly return to lurking... ;
>>>       
>> It looks like a trivial fix and the patch is here. I have just started
>> testing it myself, but if I don't send it now it will be Wednesday before
>> I do. No sign-off because I haven't verified it, but I would be delighted
>> if you would pass judgement on its efficacy. Thank you.
>>
>>     
>
> All,
>
> Applied, compiled, and tested clean on a P4 Prescott. I'll try this a
> little later on my x64. Thank you for this fix, and thank you all for
> just a fast response

We aims to please. Thank you for the work you put in. That, and everyone
who jumped in to help identify the problem.



  reply	other threads:[~2008-10-29 16:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-25  8:49 tmpfs support of xattrs? Rob MacKinnon
2008-10-25 21:59 ` H. Peter Anvin
2008-10-26 12:26 ` Hugh Dickins
2008-10-26 13:25   ` Andreas Gruenbacher
2008-10-27 20:14     ` Rob MacKinnon
2008-10-27 20:25       ` Stephen Smalley
2008-10-27 20:53         ` Andreas Gruenbacher
2008-10-27 21:12           ` Rob MacKinnon
2008-10-28  5:51             ` Casey Schaufler
2008-10-29 15:15               ` [PATCH] smack inode_listsecurity fix Casey Schaufler
2008-10-29 15:56               ` tmpfs support of xattrs? Rob MacKinnon
2008-10-29 16:12                 ` Casey Schaufler [this message]
2008-10-27 21:00         ` Rob MacKinnon
2008-10-27 21:54           ` Casey Schaufler
  -- strict thread matches above, loose matches on Subject: below --
2008-10-25  8:27 Rob MacKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49088B73.2080208@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=agruen@suse.de \
    --cc=c4blem0nkey@gmail.com \
    --cc=hpa@zytor.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.mackinnon@gmail.com \
    --cc=sds@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox