[Group.of.nepali.translators] [Bug 1714185] Re: flashcache is not usable on kernel version 4.8 and later
This bug was fixed in the package flashcache -
3.1.3+git20150701-2ubuntu3
---
flashcache (3.1.3+git20150701-2ubuntu3) xenial; urgency=medium
* Backport compat code for kernel 4.8 (LP: #1662108)
* Initialize bi_op_flags in dm_io_request structures (LP: #1714185)
* Fix DKMS compile for 4.13+ kernels (LP: #1706426)
-- Stefan Bader Mon, 06 Feb 2017 17:25:15
+0100
** Changed in: flashcache (Ubuntu Xenial)
Status: Fix Committed => 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 Released
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 "
- run "sudo mkfs.ext4 /dev/mapper/"
- run "sudo fsck -f /dev/mapper/"
- run "sudo dmsetup remove " (this can take a bit)
- run "sudo fsck -f "
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
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1714185] Re: flashcache is not usable on kernel version 4.8 and later
** 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 "
- run "sudo mkfs.ext4 /dev/mapper/"
- run "sudo fsck -f /dev/mapper/"
- run "sudo dmsetup remove " (this can take a bit)
- run "sudo fsck -f "
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
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1714185] Re: flashcache is not usable on kernel version 4.8 and later
This bug was fixed in the package flashcache -
3.1.3+git20150701-5ubuntu0.17.04.1
---
flashcache (3.1.3+git20150701-5ubuntu0.17.04.1) zesty; urgency=medium
* Initialize bi_op_flags in dm_io_request structures (LP: #1714185).
-- Stefan Bader Thu, 31 Aug 2017 10:17:56
+0200
** Changed in: flashcache (Ubuntu Zesty)
Status: Fix Committed => 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:
New
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 "
- run "sudo mkfs.ext4 /dev/mapper/"
- run "sudo fsck -f /dev/mapper/"
- run "sudo dmsetup remove " (this can take a bit)
- run "sudo fsck -f "
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
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1714185] Re: flashcache is not usable on kernel version 4.8 and later
Submitted to Debian:
873949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873949
** Bug watch added: Debian Bug tracker #873949
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873949
** Also affects: flashcache (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873949
Importance: Unknown
Status: Unknown
--
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:
In Progress
Status in flashcache source package in Zesty:
Fix Committed
Status in flashcache package in Debian:
Unknown
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 "
- run "sudo mkfs.ext4 /dev/mapper/"
- run "sudo fsck -f /dev/mapper/"
- run "sudo dmsetup remove " (this can take a bit)
- run "sudo fsck -f "
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
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1714185] Re: flashcache is not usable on kernel version 4.8 and later
This bug was fixed in the package flashcache -
3.1.3+git20150701-5ubuntu1
---
flashcache (3.1.3+git20150701-5ubuntu1) artful; urgency=medium
* Initialize bi_op_flags in dm_io_request structures (LP: #1714185).
* Fix DKMS compile for 4.13+ kernels (LP: #1706426).
-- Stefan Bader Wed, 30 Aug 2017 16:49:59
+0200
** Changed in: flashcache (Ubuntu)
Status: In Progress => 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:
In Progress
Status in flashcache source package in Zesty:
In Progress
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 "
- run "sudo mkfs.ext4 /dev/mapper/"
- run "sudo fsck -f /dev/mapper/"
- run "sudo dmsetup remove " (this can take a bit)
- run "sudo fsck -f "
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashcache/+bug/1714185/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1714185] Re: flashcache is not usable on kernel version 4.8 and later
** Also affects: flashcache (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: flashcache (Ubuntu Zesty)
Importance: Undecided
Status: New
--
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:
In Progress
Status in flashcache source package in Xenial:
In Progress
Status in flashcache source package in Zesty:
In Progress
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 "
- run "sudo mkfs.ext4 /dev/mapper/"
- run "sudo fsck -f /dev/mapper/"
- run "sudo dmsetup remove " (this can take a bit)
- run "sudo fsck -f "
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashcache/+bug/1714185/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
