From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org, KaiGai Kohei <kaigai@ak.jp.nec.com>
Subject: Re: JFFS2/xattr problems.
Date: Mon, 12 Jun 2006 20:06:53 +0200 [thread overview]
Message-ID: <20060612180653.GA17177@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1150105995.8184.17.camel@pmac.infradead.org>
On Mon, 12 June 2006 10:53:15 +0100, David Woodhouse wrote:
> On Mon, 2006-06-12 at 18:43 +0900, KaiGai Kohei wrote:
> > In my opinion, a xattr across multiple nodes isn't neccesary.
> > What do you think?
>
> I'd be happier if it worked -- some of us have plans to abuse XATTR
> support by building a simple database on it... :)
>
> But as long as the failure mode is _graceful_, I suppose we can live
> without it for now, if ext3 is also limited to 4KiB.
Seems you missed Ted's presentation at LCA this year. Among the
interesting bits:
o Pretty much anything on Linux is limited to 64KiB or less.
o Ext[23] is limited to 4KiB total for all attributes, including all
keys and all values.
o The biggest user of Alternate Streams (less-limited versions of
xattr on Windows, Solaris, etc.) arguably is root kits. Alternate
Streams have the advantage that tripwire etc. don't understand them
and won't look for malware there.
o Some system administrators have no plans to upgrade to Solaris 9
ever, because it supports Alternate Streams. The trouble of hidden
malware is not worth the gains.
Notable was also, that Ted repeated the last two points in several
variations. Not sure if I would follow his line of thought 100%, but
he does have a point.
Jörn
--
The competent programmer is fully aware of the strictly limited size of
his own skull; therefore he approaches the programming task in full
humility, and among other things he avoids clever tricks like the plague.
-- Edsger W. Dijkstra
next prev parent reply other threads:[~2006-06-12 18:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 18:41 JFFS2/xattr problems David Woodhouse
2006-05-21 3:22 ` David Woodhouse
2006-05-21 11:24 ` KaiGai Kohei
2006-05-21 11:19 ` KaiGai Kohei
2006-05-21 12:41 ` David Woodhouse
2006-06-12 2:17 ` KaiGai Kohei
2006-06-12 8:03 ` David Woodhouse
2006-06-12 9:43 ` KaiGai Kohei
2006-06-12 9:53 ` David Woodhouse
2006-06-12 18:06 ` Jörn Engel [this message]
2006-06-13 13:36 ` KaiGai Kohei
2006-06-13 14:13 ` Jörn Engel
2006-06-14 21:58 ` Theodore Tso
2006-06-15 11:47 ` Jörn Engel
2006-06-15 15:24 ` Theodore Tso
2006-06-13 13:30 ` KaiGai Kohei
2006-06-24 5:58 ` KaiGai Kohei
2006-06-24 12:44 ` David Woodhouse
2006-06-26 15:45 ` David Woodhouse
2006-06-27 2:43 ` KaiGai Kohei
2006-06-29 6:02 ` KaiGai Kohei
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=20060612180653.GA17177@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=dwmw2@infradead.org \
--cc=kaigai@ak.jp.nec.com \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox