27 Jan, 2010

1 commit

• 7e32b7bb7   fix leak in romfs_fill_super() ... Browse Code »

  Signed-off-by: Al Viro

  Al Viro

  2010-01-27 11:22:26 +0800  

24 Sep, 2009

1 commit

• a21f3c2a0   fs/romfs: correct error-handling code ... Browse Code »

  romfs_iget returns an ERR_PTR value in an error case instead of NULL.

  A simplified version of the semantic match that finds this problem is as
  follows: (http://coccinelle.lip6.fr/)

  //
  @match exists@
  expression x, E;
  statement S1, S2;
  @@

  x = romfs_iget(...)
  ... when != x = E
  (
  * if (x == NULL || ...) S1 else S2
  |
  * if (x == NULL && ...) S1 else S2
  )
  //

  Signed-off-by: Julia Lawall
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Julia Lawall

  2009-09-24 22:21:05 +0800  

22 Sep, 2009

1 commit

• 6e1d5dcc2   const: mark remaining inode_operations as const ... Browse Code »

  Signed-off-by: Alexey Dobriyan
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Alexey Dobriyan

  2009-09-22 22:17:24 +0800  

09 May, 2009

1 commit

• 774e33e70   ROMFS: romfs_dev_read() error ignored ... Browse Code »

  romfs_dev_read() may return -EIO, but ret is unsigned, so the errorpath
  isn't taken.

  Signed-off-by: Roel Kluin
  Signed-off-by: Al Viro

  Roel Kluin

  2009-05-09 22:49:41 +0800  

25 Apr, 2009

1 commit

• 84baf74bf   ROMFS: romfs_lookup() shouldn't be doing a partial name comparison ... Browse Code »

  romfs_lookup() should be using a routine akin to strcmp() on the backing store,
  rather than one akin to strncmp(). If it uses the latter, it's liable to match
  /bin/shutdown when looking up /bin/sh.

  Signed-off-by: David Howells
  Tested-by: Michal Simek
  Signed-off-by: Linus Torvalds

  David Howells

  2009-04-25 04:28:31 +0800  

07 Apr, 2009

1 commit

• 8a59f5d25   fs/romfs: return f_fsid for statfs(2) ... Browse Code »

  Make romfs return f_fsid info for statfs(2).

  Signed-off-by: Coly Li
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Coly Li

  2009-04-07 23:31:10 +0800  

24 Mar, 2009

1 commit

• da4458bda   NOMMU: Make it possible for RomFS to use MTD devices directly ... Browse Code »

  Change RomFS so that it can use MTD devices directly - without the intercession
  of the block layer - as well as using block devices.

  This permits RomFS:

  (1) to use the MTD direct mapping facility available under NOMMU conditions if
  the underlying device is directly accessible by the CPU (including XIP);

  (2) and thus to be used when the block layer is disabled.

  RomFS can be configured with support just for MTD devices, just for Block
  devices or for both. If RomFS is configured for both, then it will treat
  mtdblock device files as MTD backing stores, not block layer backing stores.

  I tested this using a CONFIG_MMU=n CONFIG_BLOCK=n kernel running on my FRV
  board with a RomFS image installed on the mtdram test device. I see my test
  program being run XIP:

  # cat /proc/maps
  ...
  c0c000b0-c0c01f8c r-xs 00000000 1f:00 144 /mnt/doshm
  ...

  GDB on the kernel can be used to show that these addresses are within the
  set-aside RAM space.

  Signed-off-by: David Howells
  Tested-by: Bernd Schmidt
  Signed-off-by: David Woodhouse

  David Howells

  2009-03-24 17:01:32 +0800