From: David Woodhouse <dwmw2@infradead.org>
To: Alexander Larsson <alex@cendio.se>
Cc: Markus Thiesmeyer <mthi@gmx.de>,
mtd@infradead.org, jffs-dev@axis.com, bmatthews@redhat.com
Subject: Re: Is JFFS a full featured filesystem?
Date: Wed, 02 Aug 2000 13:24:46 +0100 [thread overview]
Message-ID: <12414.965219086@cygnus.co.uk> (raw)
In-Reply-To: <11108.965218269@cygnus.co.uk>
dwmw2@infradead.org said:
> alex@cendio.se said:
> > All this, and the fact that the missing needed mutex around the
> > writing to the log makes the jffs filesystem quite seriously borked.
> This compiles. Wonder if it works...
Hmmm. I didn't really expect it to work without deadlocking - I expected
there to be some path from jffs_write_node() through jffs_fmalloc() to
jffs_garbage_collect() and hence jffs_rewrite_data() - which would attempt
to obtain the lock for a second time.
In fact, it seems that it does work, because there's no attempt made to
trigger immediate GC if jffs_write_node() finds that there's not enough
space. Am I on crack or is this really the case?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-08-02 12:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-01 16:15 Is JFFS a full featured filesystem? Markus Thiesmeyer
2000-08-01 18:08 ` Philipp Rumpf
2000-08-02 11:13 ` Alexander Larsson
2000-08-02 12:11 ` David Woodhouse
2000-08-02 12:24 ` David Woodhouse [this message]
2000-08-02 13:45 ` Alexander Larsson
2000-08-02 13:52 ` David Woodhouse
2000-08-02 14:20 ` David Woodhouse
2000-08-02 15:33 ` Alexander Larsson
2000-08-02 16:58 ` Philipp Rumpf
2000-08-02 14:13 ` Alexander Larsson
2000-08-02 16:50 ` Philipp Rumpf
2000-08-02 18:06 ` Alexander Larsson
2000-08-02 19:36 ` Philipp Rumpf
2000-08-02 19:57 ` Alexander Larsson
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=12414.965219086@cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=alex@cendio.se \
--cc=bmatthews@redhat.com \
--cc=jffs-dev@axis.com \
--cc=mtd@infradead.org \
--cc=mthi@gmx.de \
/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