From: Stuart Young <sgy@amc.com.au>
To: ReiserFS List <reiserfs-list@namesys.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"Nikita Danilov" <Nikita@namesys.com>,
"Andreas Dilger" <adilger@turbolabs.com>
Subject: Re: [reiserfs-list] Re: [REISERFS TESTING] new patches on ftp.namesys.com: 2.4.15-pre7
Date: Thu, 22 Nov 2001 10:30:05 +1100 [thread overview]
Message-ID: <5.1.0.14.0.20011122102342.009f7d00@mail.amc.localnet> (raw)
In-Reply-To: <20011121102517Z281563-17408+16912@vger.kernel.org>
In-Reply-To: <15355.31671.983925.611542@beta.reiserfs.com> <200111210110.fAL1Atc11275@beta.namesys.com> <20011121011655.M1308@lynx.no> <15355.31671.983925.611542@beta.reiserfs.com>
At 11:24 AM 21/11/01 +0100, Dieter Nützel wrote:
>Am Mittwoch, 21. November 2001 11:02 schrieb Nikita Danilov:
>
> > Yes, it's right, but currently we have what we have currently. I am
> > going to extend inode-attrs.patch and add new mount option
> > "noattrs". With it ioctls to set and get attributes will continue to
> > work, but attributes themselves will not have any effect. Then, one can
> > boot with "rootflags=noattrs" and read-write root, clear all attributes
> > by chattr -R and remount root.
>
>After I've 'booted into single user mode with "linux rootflags=noattrs" I
>could change my archives but _NOT_ /dev/console the right way. After the
>second reboot I got the warning and kernel hang, again. Something wrong
>with your patch or my installation?
Erm, while disabling set and get as a nice idea, you only need to disable
get. Disabling set will mean you 'cannot' reset the file that is causing
the problem, because chattr won't actually be able to do what you want.
I haven't looked at the code that chattr uses either, but you may want to
check at HOW it sets/resets values.
eg: Does it read in the value, change the bit and write it out again, or
does it just change that bit? If it reads and get is disabled, well then
you would want to make sure you set the 'full value' that needs to be
there. Not a bug so much as something that just needs to be documented.
AMC Enterprises P/L - Stuart Young
First Floor - Network and Systems Admin
3 Chesterville Rd - sgy@amc.com.au
Cheltenham Vic 3192 - Ph: (03) 9584-2700
http://www.amc.com.au/ - Fax: (03) 9584-2755
next prev parent reply other threads:[~2001-11-21 23:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200111210110.fAL1Atc11275@beta.namesys.com>
2001-11-21 8:49 ` Nikita Danilov
2001-11-21 8:16 ` [reiserfs-list] " Andreas Dilger
2001-11-21 12:58 ` Ed Tomlinson
2001-11-21 23:30 ` Stuart Young [this message]
2001-11-21 10:02 ` Nikita Danilov
2001-11-21 10:24 ` Dieter Nützel
2001-11-21 12:18 ` Nikita Danilov
2001-11-21 16:52 ` Jeff Mahoney
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=5.1.0.14.0.20011122102342.009f7d00@mail.amc.localnet \
--to=sgy@amc.com.au \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=Nikita@namesys.com \
--cc=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
/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®