Skip to content

L
linux
Switch branch/tag
  1. 19 Oct, 2004 1 commit
  3. 18 Oct, 2004 5 commits
  5. 17 Oct, 2004 7 commits
  7. 16 Oct, 2004 13 commits
  9. 15 Oct, 2004 7 commits
  11. 14 Oct, 2004 5 commits
    • Richard Russon's avatar
      Merge flatcap.org:/home/flatcap/backup/bk/ntfs-2.6 · 3a155b7e
      Richard Russon authored 
      into flatcap.org:/home/flatcap/backup/bk/ntfs-2.6-devel
      3a155b7e
    • Anton Altaparmakov's avatar
      NTFS: - Fix two race conditions in fs/ntfs/inode.c::ntfs_put_inode(). · 8f62c402
      Anton Altaparmakov authored 
      - Fix race condition in fs/ntfs/inode.c::ntfs_put_inode() by moving the
  index inode bitmap inode release code from there to
  fs/ntfs/inode.c::ntfs_clear_big_inode().  (Thanks to Christoph
  Hellwig for spotting this.)
- Fix race condition in fs/ntfs/inode.c::ntfs_put_inode() by taking the
  inode semaphore around the code thst sets ni->itype.index.bmp_ino to
  NULL and reorganize the code to optimize it a bit.  (Thanks to
  Christoph Hellwig for spotting this.)
Signed-off-by: default avatarAnton Altaparmakov <aia21@cantab.net>
      8f62c402
    • Anton Altaparmakov's avatar
      NTFS: Big cleanup of mft record writing code. · d7ca9266
      Anton Altaparmakov authored 
      - Clear the page uptodate flag in fs/ntfs/aops.c::ntfs_write_mst_block()
  to ensure noone can see the page whilst the mst fixups are applied.
- Add the helper fs/ntfs/mft.c::ntfs_may_write_mft_record() which
  checks if an mft record may be written out safely obtaining any
  necessary locks in the process.  This is used by
  fs/ntfs/aops.c::ntfs_write_mst_block().
- Modify fs/ntfs/aops.c::ntfs_write_mst_block() to also work for
  writing mft records and improve its error handling in the process.
  Now if any of the records in the page fail to be written out, all
  other records will be written out instead of aborting completely.
- Remove ntfs_mft_aops and update all users to use ntfs_mst_aops.
- Modify fs/ntfs/inode.c::ntfs_read_locked_inode() to set the
  ntfs_mst_aops for all inodes which are NInoMstProtected() and
  ntfs_aops for all other inodes.
- Rename fs/ntfs/mft.c::sync_mft_mirror{,_umount}() to
  ntfs_sync_mft_mirror{,_umount}() and change their parameters so they
  no longer require an ntfs inode to be present.  Update all callers.
- Cleanup the error handling in fs/ntfs/mft.c::ntfs_sync_mft_mirror().
- Clear the page uptodate flag in fs/ntfs/mft.c::ntfs_sync_mft_mirror()
  to ensure noone can see the page whilst the mst fixups are applied.
- Remove the no longer needed fs/ntfs/mft.c::ntfs_mft_writepage() and
  fs/ntfs/mft.c::try_map_mft_record().
- Fix callers of fs/ntfs/aops.c::mark_ntfs_record_dirty() to call it
  with the ntfs inode which contains the page rather than the ntfs
  inode the mft record of which is in the page.

Ooops.  Yes, I know, I should have split this up into smaller changes...
Signed-off-by: default avatarAnton Altaparmakov <aia21@cantab.net>
      d7ca9266
    • Linus Torvalds's avatar
      Take the whole PCI bus range into account when scanning PCI bridges. · 8b5915b0
      Linus Torvalds authored 
      A bridge that has been set up by firmware to cover multiple PCI
buses but doesn't actually have anything connected behind some of
them caused us to use the incorrect maxmimum bus number span when
scanning the bridge chip.

Problem reported by Tim Saunders, with Russell King suggesting
the fix.
      8b5915b0
    • Linus Torvalds's avatar
      Fix threaded user page write memory ordering · 538ce05c
      Linus Torvalds authored 
      Make sure we order the writes to a newly created page
with the page table update that potentially exposes the
page to another CPU.

This is a no-op on any architecture where getting the
page table spinlock will already do the ordering (notably
x86), but other architectures can care.
      538ce05c
  13. 13 Oct, 2004 2 commits
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7