mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Bernd Schubert <bernd-schubert@gmx.de>
Cc: John M Flinchbaugh <john@hjsoft.com>,
	reiserfs-list@namesys.com, Sam Vilain <sam@vilain.net>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.15 Bug? New security model?
Date: Wed, 8 Feb 2006 12:50:33 -0800	[thread overview]
Message-ID: <20060208205033.GB22771@shell0.pdx.osdl.net> (raw)
In-Reply-To: <200602081314.59639.bernd-schubert@gmx.de>

* Bernd Schubert (bernd-schubert@gmx.de) wrote:
> On Wednesday 08 February 2006 06:37, John M Flinchbaugh wrote:
> > On Wed, Feb 08, 2006 at 02:31:46PM +1300, Sam Vilain wrote:
> > > Bernd Schubert wrote:
> > > >With 2.6.15:
> > > >bathl:~# touch /var/run/test
> > > >touch: cannot touch `/var/run/test': Permission denied
> > > >With 2.6.13:
> > > >bathl:~# touch /var/run/test
> > > >(No error message)
> > >
> > > Some ideas; ACLs, SELinux, Attributes, Capabilities.
> >
> > lsattr -d /var/run && lsattr /var/run
> 
> Indeed, with 2.6.13
> 
> bathl:~# lsattr -d /var/run
> lsattr: Inappropriate ioctl for device While reading flags on /var/run
> 
> with 2.6.15.3

OK, this has a reiserfs fix for attrs support.  Rather than back it
out, I'd like to get the proper fix.

> bathl:~# cat lsatr.out.2.6.15
> --S-ia-AcBZXEj-t- /var/run
> 
> After the problem came up, I already suspected something like this and 
> therefore already had the kernel recompiled without xattr support, so I  
> don't know why lsattr shows something for 2.6.15 and nothing for 2.6.13.

attrs != xattrs

Couple of things:

1) what does 'grep attrs_cleared /proc/fs/reiserfs/on-disk-super' show?

2) does mount -o attrs ... make a difference?

thanks,
-chris

  reply	other threads:[~2006-02-08 20:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08  1:12 Bernd Schubert
2006-02-08  1:31 ` Sam Vilain
2006-02-08  5:37   ` John M Flinchbaugh
2006-02-08 12:14     ` Bernd Schubert
2006-02-08 20:50       ` Chris Wright [this message]
2006-02-08 21:46         ` Bernd Schubert
2006-02-08 22:11           ` Chris Wright
2006-02-11 21:55             ` Sergey Vlasov
2006-02-11 23:50               ` Bernd Schubert
2006-02-12 18:44                 ` Sergey Vlasov
2006-02-12 17:57               ` Jeff Mahoney
2006-02-12 19:21                 ` Sergey Vlasov
2006-02-12 23:03                   ` Bernd Schubert
2006-02-13 17:52                     ` Sergey Vlasov
2006-02-12 23:10                 ` Bernd Schubert
2006-02-13  5:47               ` Hans Reiser
2006-02-13 15:24                 ` Jeff Mahoney
2006-02-13 16:39                   ` Hans Reiser

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=20060208205033.GB22771@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=bernd-schubert@gmx.de \
    --cc=john@hjsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-list@namesys.com \
    --cc=sam@vilain.net \
    /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

all inboxes | Powered by JetHome®