An error occurred fetching the project authors.
  1. 05 Feb, 2013 1 commit
    • Jan Kara's avatar
      udf: Fix bitmap overflow on large filesystems with small block size · 89b1f39e
      Jan Kara authored
      For large UDF filesystems with 512-byte blocks the number of necessary
      bitmap blocks is larger than 2^16 so s_nr_groups in udf_bitmap overflows
      (the number will overflow for filesystems larger than 128 GB with
      512-byte blocks). That results in ENOSPC errors despite the filesystem
      has plenty of free space.
      
      Fix the problem by changing s_nr_groups' type to 'int'. That is enough
      even for filesystems 2^32 blocks (UDF maximum) and 512-byte blocksize.
      
      Reported-and-tested-by: v10lator@myway.de
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      89b1f39e
  2. 21 Sep, 2012 1 commit
  3. 04 Jan, 2012 1 commit
    • Al Viro's avatar
      udf: propagate umode_t · faa17292
      Al Viro authored
      note re mount options: fmask and dmask are explicitly truncated to 12bit,
      UDF_INVALID_MODE just needs to be guaranteed to differ from any such value.
      And umask is used only in &= with umode_t, so we ignore other bits anyway.
      Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
      faa17292
  4. 31 Oct, 2011 2 commits
  5. 06 Jan, 2011 2 commits
  6. 02 Apr, 2009 5 commits
    • Jan Kara's avatar
      udf: Don't write integrity descriptor too often · 146bca72
      Jan Kara authored
      We update information in logical volume integrity descriptor after each
      allocation (as LVID contains free space, number of directories and files on
      disk etc.). If the filesystem is on some phase change media, this leads to its
      quick degradation as such media is able to handle only 10000 overwrites or so.
      We solve the problem by writing new information into LVID only on umount,
      remount-ro and sync. This solves the problem at the price of longer media
      inconsistency (previously media became consistent after pdflush flushed dirty
      LVID buffer) but that should be acceptable.
      
      Report by and patch written in cooperation with
      Rich Coe <Richard.Coe@med.ge.com>.
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      146bca72
    • Jan Kara's avatar
      udf: Try anchor in block 256 first · 40346005
      Jan Kara authored
      Anchor block can be located at several places on the medium. Two of the
      locations are relative to media end which is problematic to detect. Also
      some drives report some block as last but are not able to read it or any
      block nearby before it. So let's first try block 256 and if it is all fine,
      don't look at other possible locations of anchor blocks to avoid IO errors.
      This change required a larger reorganization of code but the new code is
      hopefully more readable and definitely shorter.
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      40346005
    • Clemens Ladisch's avatar
      udf: use hardware sector size · 1197e4df
      Clemens Ladisch authored
      This patch makes the UDF FS driver use the hardware sector size as the
      default logical block size, which is required by the UDF specifications.
      While the previous default of 2048 bytes was correct for optical disks,
      it was not for hard disks or USB storage devices, and made it impossible
      to use such a device with the default mount options.  (The Linux mkudffs
      tool uses a default block size of 2048 bytes even on devices with
      smaller hardware sectors, so this bug is unlikely to be noticed unless
      UDF-formatted USB storage devices are exchanged with other OSs.)
      
      To avoid regressions for people who use loopback optical disk images or
      who used the (sometimes wrong) defaults of mkudffs, we also try with
      a block size of 2048 bytes if no anchor was found with the hardware
      sector size.
      Signed-off-by: default avatarClemens Ladisch <clemens@ladisch.de>
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      1197e4df
    • Marcin Slusarz's avatar
      udf: fix default mode and dmode options handling · 87bc730c
      Marcin Slusarz authored
      On x86 (and several other archs) mode_t is defined as "unsigned short"
      and comparing unsigned shorts to negative ints is broken (because short
      is promoted to int and then compared). Fix it.
      Reported-and-tested-by: default avatarLaurent Riffard <laurent.riffard@free.fr>
      Signed-off-by: default avatarMarcin Slusarz <marcin.slusarz@gmail.com>
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      87bc730c
    • Marcin Slusarz's avatar
      udf: implement mode and dmode mounting options · 7ac9bcd5
      Marcin Slusarz authored
      "dmode" allows overriding permissions of directories and
      "mode" allows overriding permissions of files.
      Signed-off-by: default avatarMarcin Slusarz <marcin.slusarz@gmail.com>
      Cc: Jan Kara <jack@suse.cz>
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      7ac9bcd5
  7. 17 Apr, 2008 3 commits
    • Jan Kara's avatar
      udf: Add read-only support for 2.50 UDF media · bfb257a5
      Jan Kara authored
      This patch implements parsing of metadata partitions and reading of Metadata
      File thus allowing to read UDF 2.50 media. Error resilience is implemented
      through accessing the Metadata Mirror File in case the data the Metadata File
      cannot be read. The patch is based on the original patch by Sebastian Manciulea
      <manciuleas@yahoo.com> and Mircea Fedoreanu <mirceaf_spl@yahoo.com>.
      Signed-off-by: default avatarSebastian Manciulea <manciuleas@yahoo.com>
      Signed-off-by: default avatarMircea Fedoreanu <mirceaf_spl@yahoo.com>
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      bfb257a5
    • Jan Kara's avatar
      udf: Cleanup anchor block detection. · 423cf6dc
      Jan Kara authored
      UDF anchor block detection is complicated by several things - there are several
      places where the anchor point can be, some of them relative to the last
      recorded block which some devices report wrongly. Moreover some devices on some
      media seem to have 7 spare blocks sectors for every 32 blocks (at least as far
      as I understand the old code) so we have to count also with that possibility.
      
      This patch splits anchor block detection into several functions so that it is
      clearer what we actually try to do. We fix several bugs of the type "for such
      and such media, we fail to check block blah" as a result of the cleanup.
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      423cf6dc
    • Christoph Hellwig's avatar
      udf: move headers out include/linux/ · 15aebd28
      Christoph Hellwig authored
      There's really no reason to keep udf headers in include/linux as they're
      not used by anything but fs/udf/.
      
      This patch merges most of include/linux/udf_fs_i.h into fs/udf/udf_i.h,
      include/linux/udf_fs_sb.h into fs/udf/udf_sb.h and
      include/linux/udf_fs.h into fs/udf/udfdecl.h.
      
      The only thing remaining in include/linux/ is a stub of udf_fs_i.h
      defining the four user-visible udf ioctls.  It's also moved from
      unifdef-y to headers-y because it can be included unconditionally now.
      Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      15aebd28
  8. 08 Feb, 2008 5 commits
  9. 31 Jul, 2007 1 commit
  10. 22 Jul, 2007 1 commit
  11. 19 Jul, 2007 1 commit
  12. 08 May, 2007 1 commit
  13. 08 Mar, 2006 1 commit
    • Phillip Susi's avatar
      [PATCH] udf: fix uid/gid options and add uid/gid=ignore and forget options · 4d6660eb
      Phillip Susi authored
      Fix a bug in udf where it would write uid/gid = 0 to the disk for files
      owned by the id given with the uid=/gid= mount options.  It also adds 4 new
      mount options: uid/gid=forget and uid/gid=ignore.  Without any options the
      id in core and on disk always match.  Giving uid/gid=nnn specifies a
      default ID to be used in core when the on disk ID is -1.  uid/gid=ignore
      forces the in core ID to allways be used no matter what the on disk ID is.
      uid/gid=forget forces the on disk ID to always be written out as -1.
      
      The use of these options allows you to override ownerships on a disk or
      disable ownwership information from being written, allowing the media to be
      used portably between different computers and possibly different users
      without permissions issues that would require root to correct.
      Signed-off-by: default avatarPhillip Susi <psusi@cfl.rr.com>
      Cc: Pekka Enberg <penberg@cs.helsinki.fi>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      4d6660eb
  14. 07 Nov, 2005 1 commit
  15. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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!
      1da177e4