Skip to content

L
linux
Switch branch/tag
  1. 29 Apr, 2006 1 commit
    • Daniel Drake's avatar
      mtd: SC520CDP should depend on MTD_CONCAT · fbbc21c6
      Daniel Drake authored 
      Toralf Förster found a compile error when CONFIG_MTD_SC520CDP=y and
CONFIG_MTD_CONCAT=n:

drivers/built-in.o: In function `init_sc520cdp':
sc520cdp.c:(.init.text+0xb4de): undefined reference to `mtd_concat_create'
drivers/built-in.o: In function `cleanup_sc520cdp':
sc520cdp.c:(.exit.text+0x14bc): undefined reference to `mtd_concat_destroy'

This patch fixes it.
Signed-off-by: default avatarDaniel Drake <dsd@gentoo.org>
Signed-off-by: default avatarJosh Boyer <jwboyer@gmail.com>
      fbbc21c6
  3. 19 Apr, 2006 1 commit
    • Joern Engel's avatar
      mtd: improve parameter parsing for block2mtd · 954c2422
      Joern Engel authored 
      Expand the parameter parsing for block2mtd.  It now accepts:
Ki, Mi, Gi	- the official prefixes for binary multiples,
		  see http://physics.nist.gov/cuu/Units/binary.html,
ki		- mistake on my side and analog to "k" for decimal multiples,
KiB, MiB, GiB	- for people that prefer to add a "B" for byte,
kiB		- combination of the above.

There were complaints about not accepting "k" for 1024.  This has long
been common practice, but is known to lead to confusion.  Hence the new
SI units and hence block2mtd only accepts units that cannot be confused
with decimal units.  Diverging from common practice doesn't always please
people, even if the change is for the better.
Signed-off-by: default avatarJoern Engel <joern@wohnheim.fh-wedel.de>
Cc: David Woodhouse <dwmw2@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      954c2422
  5. 18 Apr, 2006 2 commits
  7. 17 Apr, 2006 6 commits
  9. 16 Apr, 2006 1 commit
    • David Woodhouse's avatar
      [JFFS2] Fix race in post-mount node checking · d96fb997
      David Woodhouse authored 
      For a while now, we've postponed CRC-checking of data nodes to be done
by the GC thread, instead of being done while the user is waiting for
mount to finish. The GC thread would iterate through all the inodes on
the system and check each of their data nodes. It would skip over inodes
which had already been used or were already being read in by
read_inode(), because their data nodes would have been examined anyway.

However, we could sometimes reach the end of the for-each-inode loop and
still have some unchecked space left, if an inode we'd skipped was
_still_ in the process of being read. This fixes that race by actually
waiting for read_inode() to finish rather than just moving on.

Thanks to Ladislav Michl for coming up with a reproducible test case and
helping to track it down.
Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      d96fb997
  11. 15 Apr, 2006 14 commits
  13. 14 Apr, 2006 15 commits
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7