From: David Newall <david@davidnewall.com>
To: Dave Jones <davej@redhat.com>,
Antoine Martin <antoine@nagafix.co.uk>,
tytso@thunk.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: bug in fsck or ext2/ext3?
Date: Tue, 25 Sep 2007 03:46:25 +0930 [thread overview]
Message-ID: <46F7FEF9.2070702@davidnewall.com> (raw)
In-Reply-To: <20070924170439.GF8127@redhat.com>
Dave Jones wrote:
> On Mon, Sep 24, 2007 at 05:56:39PM +0100, Antoine Martin wrote:
>
> > # rm -fr tmp/chroot.broken
> > rm: cannot remove directory (...)
> > Same result when trying to do anything to those files chown/chmod/touch:
> > "Operation not permitted"
>
> Various files in the directories it complains about have their 'i'
> bit set. lsattr will show you. chattr -i those files, and the
> directory is removable again.
Additionally, this is a classic symptom of malware. A directory named
"..." is a big hint.
next prev parent reply other threads:[~2007-09-24 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 16:56 bug in fsck or ext2/ext3? Antoine Martin
2007-09-24 17:04 ` Dave Jones
2007-09-24 18:16 ` David Newall [this message]
2007-09-24 18:21 ` Dave Jones
2007-09-24 17:14 ` Alistair John Strachan
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=46F7FEF9.2070702@davidnewall.com \
--to=david@davidnewall.com \
--cc=antoine@nagafix.co.uk \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@thunk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.