← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1656259] Re: Linux ZFS port doesn't respect RLIMIT_FSIZE

 

This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu16

---------------
zfs-linux (0.6.5.6-0ubuntu16) xenial; urgency=medium

  * Enable zfs to respect RSIZE_LIMIT limits (LP: #1656259)
    - backport of zfs upstream commit 4b908d32200b6e5c7b5115322b6c8d25e770daa0
      ("Linux 4.8 compat: posix_acl_valid()") to facilitate changes in posix_acl_valid.
      1015-Linux-4.8-compat-posix_acl_valid.patch
    - backport of upstream commit 933ec999511f3d29de005bfa8966ae007b161c0f
      ("Retire .write/.read file operations")
      1016-Retire-.write-.read-file-operations.patch

 -- Colin Ian King <colin.king@xxxxxxxxxxxxx>  Fri, 17 Feb 2017 11:00:12
+0000

** Changed in: zfs-linux (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/1656259

Title:
  Linux ZFS port doesn't respect RLIMIT_FSIZE

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed
Status in zfs-linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
Status in zfs-linux source package in Zesty:
  Fix Released

Bug description:
  == SRU Request, Yakkety, Xenial ==

  bash -c 'ulimit -f 1024; yes | head -n2097152'
  >/path/on/filesystem/under/test

  On ext4, this test case prints something along the lines of:

    bash: line 1: 11274 Broken pipe             yes
         11275 File size limit exceeded(core dumped) | head -n2097152

  On ZFS, this test case incorrectly exits zero with no output,
  demonstrating that ZFS does not respect RLIMIT_FSIZE.

  I asked a friend to run this on Solaris 5.10 and FreeBSD 10.0-CURRENT,
  and on those systems this test case correctly generates SIGXFSZ; so it
  seems that this is a bug in the Linux port of ZFS.

  (This was discovered while tracking down Launchpad test suite failures
  under LXD on ZFS.  Launchpad uses RLIMIT_FSIZE in one place to guard
  against bugs that cause debdiff to generate arbitrarily large amounts
  of output and fill the disk.)

  == Fix ==

  Upstream fix
  https://github.com/behlendorf/zfs/commit/230c03e59d3d13d9b60125f73cf3fff327b45c21

  == Test case ==

  With the fix:

  bash -c 'ulimit -f 1024; yes | head -n2097152'
  >/path/on/filesystem/under/test

  should report:

    bash: line 1: 11274 Broken pipe             yes
         11275 File size limit exceeded(core dumped) | head -n2097152

  == Regression Potential ==

  Could break read/writes semantics to zfs

  --------------------------------------

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 13 10:01:36 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=139ad421-b014-4c34-ae8c-dd1d15205875
  InstallationDate: Installed on 2013-03-01 (1413 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1)
  MachineType: LENOVO 20BXCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=12c52021-a1ab-4984-9dd7-63cf0dcaac16 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware                            1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET49WW (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1656259/+subscriptions