group.of.nepali.translators team mailing list archive

[Bug Watch Updater <1714185@xxxxxxxxxxxxxxxxxx>]

** Changed in: flashcache (Debian)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1714185

Title:
  flashcache is not usable on kernel version 4.8 and later

Status in flashcache package in Ubuntu:
  Fix Released
Status in flashcache source package in Xenial:
  Fix Committed
Status in flashcache source package in Zesty:
  Fix Released
Status in flashcache package in Debian:
  Fix Released

Bug description:
  SRU justification:

  Impact:
  The flashcache DKMS module is building but due to an incomplete adaptation for the bi_op/bi_opf split the resulting device-mapper logical volume is not properly writing back data to the backing device.
  !!! It is possible to write to the volume but the data is LOST !!!

  Fix:
  When setting up internal device-mapper IO structures we *must* also initialize bi_op_flags. At least when the structure is on the stack and is set up with individual assignments. Maybe it would not be required for the { ... } form but better be explicit in all cases.

  Testcase:
  - prereq: two block devices (disks or partitions), for testing this can also
    be loop devices. also need flashcache-utils and flashcache-dkms
  - run "sudo flashcache-create -p back <name> <cache-dev> <backing-dev>"
  - run "sudo mkfs.ext4 /dev/mapper/<name>"
  - run "sudo fsck -f /dev/mapper/<name>"
  - run "sudo dmsetup remove <name>" (this can take a bit)
  - run "sudo fsck -f <backing-dev>"

  Regression Potential:
  None. The fix is only properly initializing otherwise uninitialized struct fields.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashcache/+bug/1714185/+subscriptions