[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[dm-devel] Patchset 2.5.63-dm-1



http://people.sistina.com/~thornber/patches/2.5-stable/2.5.63/2.5.63-dm-1.tar.bz2

Changes from 2.5.63
-------------------

Revision 1:
  When reloading a device the ioctl interface was forgetting to drop a
  reference on the new table.

Revision 2:
  Fix __LOW macro.  [Kevin Corry]

Revision 3:
  Use the correct size for "name" in register_with_devfs().
  
  During Al Viro's devfs cleanup a few versions ago, this function was
  rewritten, and the "name" string added. The 32-byte size is not large
  enough to prevent a possible buffer overflow in the sprintf() call,
  since the hash cell can have a name up to 128 characters.
  
  [Kevin Corry]

Revision 4:
  Fix problem with devfs when unloading the dm module.
  
  dm-ioctl.c: deregister the misc device, and its associated symlink
  *before* removing the /dev/mapper dir.  [Alasdair Kergon]

Revision 5:
  Silly mistake in error path when an unknown target type is requested.

Revision 6:
  Allow slashes ('/') within a DM device name, but not at the beginning.
  
  Devfs will automatically create all necessary sub-directories if a name
  with embedded slashes is registered.  [Kevin Corry]

Revision 7:
  Another fix for the __LOW macro.
  
  When dm_table and dm_target structures are initialized, the "limits" fields 
  (struct io_restrictions) are initialized to zero (e.g. in dm_table_add_target()
  in dm-table.c). However, zero is not a useable value in these fields. The
  request queue will never let an I/O through, regardless of how small it might
  be, if max_sectors is set to zero (see generic_make_request in ll_rw_blk.c).
  This change to the __LOW() macro sets these fields correctly when they are
  first initialized.  [Kevin Corry]

Revision 8:
  Return correct error codes from dm_table_add_target().  [Kevin Corry]



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]