04 Dec, 2010
1 commit
-
Signed-off-by: Joe Perches
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse
25 Oct, 2010
1 commit
-
When JFFS2 is used for large volumes, the mount times are quite long.
Increasing the hash size provides a significant speed boost on the OLPC
XO-1 laptop.Add logic that dynamically selects a hash size based on the size of
the medium. A 64mb medium will result in a hash size of 128, and a 512mb
medium will result in a hash size of 1024.Signed-off-by: Daniel Drake
Signed-off-by: David Woodhouse
08 Aug, 2010
1 commit
-
Signed-off-by: David Woodhouse
02 May, 2008
1 commit
-
To support NFS export, we need to know the parent inode of directories.
Rather than growing the jffs2_inode_cache structure, share space with
the nlink field -- which was always set to 1 for directories anyway.Signed-off-by: David Woodhouse
23 Apr, 2008
1 commit
-
Just to keep the debug code happy when it's adding all the blocks up.
Otherwise, they disappear for a while while the locks are dropped to
check them and write the cleanmarker.Signed-off-by: David Woodhouse
13 Oct, 2007
1 commit
-
Instead of matching resv_blocks_gcmerge, which is only about 3, instead
match resv_blocks_gctrigger, which includes a proportion of the total
device size.These ought to become tunable from userspace, at some point.
Signed-off-by: David Woodhouse
07 Oct, 2007
1 commit
-
With huge amounts of free space, we weren't bothering to GC for while a
while, and pathological numbers of obsolete nodes were accumulating,
seriously affecting performance on NAND flash (OLPC trac #3978)Signed-off-by: David Woodhouse
25 Apr, 2007
1 commit
-
In particular, remove the bit in the LICENCE file about contacting
Red Hat for alternative arrangements. Their errant IS department broke
that arrangement a long time ago -- the policy of collecting copyright
assignments from contributors came to an end when the plug was pulled on
the servers hosting the project, without notice or reason.We do still dual-license it for use with eCos, with the GPL+exception
licence approved by the FSF as being GPL-compatible. It's just that nobody
has the right to license it differently.Signed-off-by: David Woodhouse
09 Feb, 2007
1 commit
-
If jffs2_sum_init() fails, c->blocks is not freed neither in
jffs2_do_mount_fs() nor in jffs2_do_fill_super().Signed-off-by: Dmitry Adamushko
Signed-off-by: David Woodhouse
13 May, 2006
1 commit
-
This attached patches provide xattr support including POSIX-ACL and
SELinux support on JFFS2 (version.5).There are some significant differences from previous version posted
at last December.
The biggest change is addition of EBS(Erase Block Summary) support.
Currently, both kernel and usermode utility (sumtool) can recognize
xattr nodes which have JFFS2_NODETYPE_XATTR/_XREF nodetype.In addition, some bugs are fixed.
- A potential race condition was fixed.
- Unexpected fail when updating a xattr by same name/value pair was fixed.
- A bug when removing xattr name/value pair was fixed.The fundamental structures (such as using two new nodetypes and exclusion
mechanism by rwsem) are unchanged. But most of implementation were reviewed
and updated if necessary.
Espacially, we had to change several internal implementations related to
load_xattr_datum() to avoid a potential race condition.[1/2] xattr_on_jffs2.kernel.version-5.patch
[2/2] xattr_on_jffs2.utils.version-5.patchSigned-off-by: KaiGai Kohei
Signed-off-by: David Woodhouse
15 Jan, 2006
1 commit
-
Remove the "inline" keyword from a bunch of big functions in the kernel with
the goal of shrinking it by 30kb to 40kbSigned-off-by: Arjan van de Ven
Signed-off-by: Ingo Molnar
Acked-by: Jeff Garzik
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
07 Nov, 2005
8 commits
-
Signed-off-by: Thomas Gleixner
-
Signed-off-by: Artem B. Bityutskiy
Signed-off-by: Thomas Gleixner -
Simplify the debugging code further.
Update the TODO listSigned-off-by: Artem B. Bityutskiy
Signed-off-by: Thomas Gleixner -
Signed-off-by: Ferenc Havasi
Signed-off-by: Thomas Gleixner -
The goal of summary is to speed up the mount time. Erase block summary (EBS)
stores summary information at the end of every (closed) erase block. It is
no longer necessary to scan all nodes separetly (and read all pages of them)
just read this "small" summary, where every information is stored which is
needed at mount time.This summary information is stored in a JFFS2_FEATURE_RWCOMPAT_DELETE. During
the mount process if there is no summary info the orignal scan process will
be executed. EBS works with NAND and NOR flashes, too.There is a user space tool called sumtool to generate this summary
information for a JFFS2 image.Signed-off-by: Ferenc Havasi
Signed-off-by: Thomas Gleixner -
Remove support for virtual blocks, which are build by
concatenation of multiple physical erase blocks.For more information please read the MTD mailing list thread
"[PATCH] remove support for virtual blocks"Signed-off-by: Ferenc Havasi
Signed-off-by: Thomas Gleixner -
The debug code cleanup broke the eCos build.
Signed-off-by: Andrew Lunn
Signed-off-by: Thomas Gleixner -
Various simplifiactions. printk format corrections.
Convert more code to use the new debug functions.Signed-off-by: Artem B. Bityutskiy
Signed-off-by: Thomas Gleixner
06 Nov, 2005
2 commits
-
If debugging is disabled, define debugging functions as empty macros, instead
of using Dx() explicitly.Signed-off-by: Artem B. Bityutskiy
Signed-off-by: Thomas Gleixner -
Move debug functions into a seperate source file
Signed-off-by: Artem B. Bityutskiy
Signed-off-by: Thomas Gleixner
13 Jul, 2005
1 commit
-
In case of a mount error locks might be uninitialized but
accessed by the resulting call to jffs2_kill_sb().Signed-off-by: Artem B. Bityuckiy
Signed-off-by: Thomas Gleixner
23 May, 2005
1 commit
-
Fix fairly sad NOR-specific bug - during FS building ic->scan_dents
isn't zero, but jffs2_mark_node_obsolete() migt be called it tries to
finde the ic corresponding to ref - this requires ic->scan_dents = 0.Signed-off-by: Artem B. Bityuckiy
Signed-off-by: Thomas Gleixner
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!
