** Description changed:

+ ### DRAFT ####
+ [Impact] 
+ 
+  * Under certains condition (such as when selinux is enabled) xfsprogs
+ on Trusty may report a error "illegal inode type" and SIGABRT,
+ generating a coredump as follow :
+ 
+ sing host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
+ Core was generated by `xfs_logprint -c /dev/mapper/image-glance'.
+ Program terminated with signal SIGABRT, Aborted.
+ 
+ [Test Case]
+ 
+ 1) Create a XFS device (dev/vdb1) 
+ 2) Remove apparmor 
+ 3) Installed selinux 
+ 4) Run xfs_logprint against /dev/vdb1 
+    - sudo xfs_logprint -c /dev/vdb1 
+ 
+ There is probably other ways but that is the one I used based on the git
+ commit log:
+ 
+ "I've tested this by a simple test such as creating one
+ file on an selinux box, so that data+attr is set, and
+ logprinting"
+ 
+ [Regression Potential]
+ 
+  * This is a rework of "xlog_print_trans_inode()" to handle more than one 
flag on f->ilf_fields if set in order to stop going in error and abort when 
facing the situation. 
+    The change has been there for a while now (Jan 2013). It never land in 
Trusty because the package it has was a copy from it's predecessor release, 
saucy.
+ 
+ [Other Info]
+  
+  * Upstream commit: 
+ https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=dda4129
+ 
+  * Trusty AFFECTED ONLY.
+  * git describe --contains dda4129
+ v3.1.11~29
+ 
+  * rmadison xfsprogs
+  xfsprogs | 3.1.9ubuntu2        | trusty
+  xfsprogs | 4.3.0+nmu1ubuntu1   | xenial
+  xfsprogs | 4.3.0+nmu1ubuntu1.1 | xenial-updates
+  xfsprogs | 4.9.0+nmu1ubuntu1   | artful
+  xfsprogs | 4.9.0+nmu1ubuntu1   | bionic
+ 
+ [Orig Description]
  It has been brought to my attention that the following :
  
  "
  The command 'xfs_logprint -c <DEVICE>' coredump on Trusty and display the 
error :
  xlog_print_trans_inode: illegal inode type
  "

** Description changed:

  ### DRAFT ####
- [Impact] 
+ [Impact]
  
-  * Under certains condition (such as when selinux is enabled) xfsprogs
+  * Under certains condition (such as when selinux is enabled) xfsprogs
  on Trusty may report a error "illegal inode type" and SIGABRT,
  generating a coredump as follow :
  
  sing host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `xfs_logprint -c /dev/mapper/image-glance'.
  Program terminated with signal SIGABRT, Aborted.
  
  [Test Case]
  
- 1) Create a XFS device (dev/vdb1) 
- 2) Remove apparmor 
- 3) Installed selinux 
- 4) Run xfs_logprint against /dev/vdb1 
-    - sudo xfs_logprint -c /dev/vdb1 
+ 1) Create a XFS device (dev/vdb1)
+ 2) Remove apparmor
+ 3) Installed selinux
+ 4) Run xfs_logprint against /dev/vdb1
+    - sudo xfs_logprint -c /dev/vdb1
  
  There is probably other ways but that is the one I used based on the git
  commit log:
  
  "I've tested this by a simple test such as creating one
  file on an selinux box, so that data+attr is set, and
  logprinting"
  
  [Regression Potential]
  
-  * This is a rework of "xlog_print_trans_inode()" to handle more than one 
flag on f->ilf_fields if set in order to stop going in error and abort when 
facing the situation. 
-    The change has been there for a while now (Jan 2013). It never land in 
Trusty because the package it has was a copy from it's predecessor release, 
saucy.
+  * This is a rework of "xlog_print_trans_inode()" to handle more than
+ one flag on f->ilf_fields if set in order to stop going in error and
+ abort when facing the situation. The change has been there for a while
+ now (Jan 2013). It never land in Trusty because the package it has was a
+ copy from it's predecessor release, saucy.
  
  [Other Info]
-  
-  * Upstream commit: 
+ 
+  * Upstream commit:
  https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=dda4129
  
-  * Trusty AFFECTED ONLY.
-  * git describe --contains dda4129
+  * Trusty AFFECTED ONLY.
+  * git describe --contains dda4129
  v3.1.11~29
  
-  * rmadison xfsprogs
-  xfsprogs | 3.1.9ubuntu2        | trusty
-  xfsprogs | 4.3.0+nmu1ubuntu1   | xenial
-  xfsprogs | 4.3.0+nmu1ubuntu1.1 | xenial-updates
-  xfsprogs | 4.9.0+nmu1ubuntu1   | artful
-  xfsprogs | 4.9.0+nmu1ubuntu1   | bionic
+  * rmadison xfsprogs
+  xfsprogs | 3.1.9ubuntu2        | trusty
+  xfsprogs | 4.3.0+nmu1ubuntu1   | xenial
+  xfsprogs | 4.3.0+nmu1ubuntu1.1 | xenial-updates
+  xfsprogs | 4.9.0+nmu1ubuntu1   | artful
+  xfsprogs | 4.9.0+nmu1ubuntu1   | bionic
  
  [Orig Description]
  It has been brought to my attention that the following :
  
  "
  The command 'xfs_logprint -c <DEVICE>' coredump on Trusty and display the 
error :
  xlog_print_trans_inode: illegal inode type
  "

** Also affects: xfsprogs (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Changed in: xfsprogs (Ubuntu)
       Status: New => Fix Released

** Description changed:

  ### DRAFT ####
  [Impact]
  
   * Under certains condition (such as when selinux is enabled) xfsprogs
  on Trusty may report a error "illegal inode type" and SIGABRT,
  generating a coredump as follow :
  
  sing host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `xfs_logprint -c /dev/mapper/image-glance'.
  Program terminated with signal SIGABRT, Aborted.
  
  [Test Case]
  
  1) Create a XFS device (dev/vdb1)
- 2) Remove apparmor
- 3) Installed selinux
- 4) Run xfs_logprint against /dev/vdb1
+ 2) apt-get dist-upgrade
+ 3) Remove apparmor
+ 4) Reboot
+ 5) Installed selinux
+ 6) Reboot
+ 7) Run xfs_logprint against /dev/vdb1
     - sudo xfs_logprint -c /dev/vdb1
  
  There is probably other ways but that is the one I used based on the git
  commit log:
  
  "I've tested this by a simple test such as creating one
  file on an selinux box, so that data+attr is set, and
  logprinting"
  
  [Regression Potential]
  
   * This is a rework of "xlog_print_trans_inode()" to handle more than
  one flag on f->ilf_fields if set in order to stop going in error and
  abort when facing the situation. The change has been there for a while
  now (Jan 2013). It never land in Trusty because the package it has was a
  copy from it's predecessor release, saucy.
  
  [Other Info]
  
   * Upstream commit:
  https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/commit/?id=dda4129
  
   * Trusty AFFECTED ONLY.
   * git describe --contains dda4129
  v3.1.11~29
  
   * rmadison xfsprogs
   xfsprogs | 3.1.9ubuntu2        | trusty
   xfsprogs | 4.3.0+nmu1ubuntu1   | xenial
   xfsprogs | 4.3.0+nmu1ubuntu1.1 | xenial-updates
   xfsprogs | 4.9.0+nmu1ubuntu1   | artful
   xfsprogs | 4.9.0+nmu1ubuntu1   | bionic
  
  [Orig Description]
  It has been brought to my attention that the following :
  
  "
  The command 'xfs_logprint -c <DEVICE>' coredump on Trusty and display the 
error :
  xlog_print_trans_inode: illegal inode type
  "

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763086

Title:
  xfs_logprint  can't handle multiply-logged inode fields

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to