[Group.of.nepali.translators] [Bug 1865967] Re: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
** Changed in: ubuntu-kernel-tests 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/1865967 Title: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: == SRU Justification == The fill_fs test for XFS in fallocate06 from ubuntu_ltp_syscalls will fail on X/B/D/E: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 8192) fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Fix == * e093c4be (xfs: Fix tail rounding in xfs_alloc_file_space()) This patch can be cherry-picked in D/E and needs some minor context adjustmest on X/B. == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1865967-xfs-fallocate06/ All patched kernels are working as expected, this issue will no longer exist on XFS: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop5 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Regression Potential == Low, this ensures all the
[Group.of.nepali.translators] [Bug 1864092] Re: quotactl07 from ubuntu_ltp_syscalls failed
Passed with Bionic 4.15.0-94.95 startup='Fri Mar 27 00:58:32 2020' tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-4.15.0-94-generic' tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:90: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s quotactl07.c:32: PASS: Q_XQUOTARM has quota type check Summary: passed 1 failed 0 skipped 0 warnings 0 tag=quotactl07 stime=1585270712 dur=1 exit=exited stat=0 core=no cu=0 cs= ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Changed in: ubuntu-kernel-tests 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/1864092 Title: quotactl07 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: == SRU Justification == This quotactl07 is a new test case added in LTP test suite, The test will fail with: <<>> incrementing stop tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-38-generic' tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop4' tst_mkfs.c:90: INFO: Formatting /dev/loop4 with xfs opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 == Fix == * 3dd4d40b (xfs: Sanity check flags of Q_XQUOTARM call) Focal got this patch from stable update. This patch can be cherry- picked into all the other kernels. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1864092-quotactl07/ All patched kernels are working as expected, == Regression Potential == Low, change limited to quota on XFS, and it's just adding a check for the flags. == Original Bug Report == Initially Found: Cloud: GCP Kernel: 5.0.0-1032.33 Test: ubuntu_ltp_syscalls 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:24 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1032-gcp' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop2' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] Summary: 02/20 15:04:55 DEBUG| utils:0153| [stdout] passed 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] failed 1 02/20 15:04:55 DEBUG| utils:0153| [stdout] skipped 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] warnings 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] tag=quotactl07 stime=1582210164 dur=4 exit=exited stat=1 core=no cu=0 cs=0 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:29 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] read01.c:24: PASS: read(2) returned 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864092/+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 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module
** Changed in: autopkgtest-cloud
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/1847816
Title:
storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
that don't include scsi_debug module
Status in autopkgtest-cloud:
Fix Released
Status in linux-kvm package in Ubuntu:
New
Status in systemd package in Ubuntu:
Fix Released
Status in linux-kvm source package in Xenial:
New
Status in systemd source package in Xenial:
In Progress
Status in linux-kvm source package in Bionic:
New
Status in systemd source package in Bionic:
Fix Released
Status in linux-kvm source package in Disco:
New
Status in systemd source package in Disco:
Won't Fix
Status in linux-kvm source package in Eoan:
New
Status in systemd source package in Eoan:
Fix Released
Status in linux-kvm source package in Focal:
New
Status in systemd source package in Focal:
Fix Released
Bug description:
Note: this bug touches on multiple packages:
- autopkgtest-cloud: merge request open to install 'modules-extra' package
- systemd: update autopkgtest to skip test if scsi_debug module isn't
available (SRU template below is for this change)
- linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have
scsi_debug module built for this kernel
[SRU template for systemd]
[impact]
the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
can't load it (and it's not built-in), the test fails. On some custom
kernels, this module is included in the new 'linux-modules-extra-*'
deb which isn't installed by default, so the test always fails when
doing a reverse-dep autopkgtest using such a kernel's meta pkg.
Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
disabled entirely; for those kernels, it will never be possible to
load the scsi_debug module and the test should be skipped.
[test case]
run the 'storage' autopkgtest with a custom kernel that doesn't
provide the scsi_debug module in the standard linux-modules deb, or
check the autopkgtest.u.c history, for example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz
[regression potential]
as this modifies one of the autopkgtest --setup-commands, a regression
would most likely cause immediate test failure due to failing to
install the proper linux-* debs.
For the systemd 'storage' test change, this only skips the test if the
scsi_debug module can't be loaded (and isn't already present, i.e.
loaded or built-in). Any regression potential from that is low, but
likely would involve incorrect test skips and/or missing valid
problems due to skipping the test.
[scope]
systemd in all releases needs to have its 'storage' test updated
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+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 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
** Changed in: sudo (Ubuntu Disco) Status: In Progress => Won't Fix ** Changed in: sudo (Ubuntu Cosmic) Status: In Progress => Won't Fix ** Changed in: sudo (Ubuntu Bionic) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: sudo (Ubuntu Xenial) Assignee: Dan Streetman (ddstreet) => (unassigned) -- 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/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in Release Notes for Ubuntu: New Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: In Progress Status in sudo source package in Bionic: In Progress Status in sudo source package in Cosmic: Won't Fix Status in sudo source package in Disco: Won't Fix Status in sudo source package in Eoan: Fix Released Bug description: [impact] sudo does not set HOME to the target user's HOME [test case] ddstreet@thorin:~$ sudo printenv | grep HOME HOME=/home/ddstreet [regression potential] this is a significant behavior change. As mentioned in comment 11 (and later, and other bugs duped to this, and the mailing list discussion, etc) users of Ubuntu so far have been used to running sudo with their own HOME set, not root's HOME. Therefore, it's inappropriate to change this behavior for existing releases; this should be changed starting in Eoan, and only the sudo and sudoers man pages changed in previous releases to indicate the actual behavior of sudo in those releases. [other info] Shortly after upstream changed the behavior, the patch to keep HOME as the calling (instead of target) user was added in bug 760140. For quick reference to anyone coming to this bug, the pre-19.10 behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home or, run sudo with the -H param. -- original description: -- I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1556302/+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 1842947] Re: dpkg 1.19.0.5ubuntu2.2 build did not recreate 'configure' file, losing changes in 'configure.ac'
Removing myself as bug owner, and marking as 'incomplete' as this is waiting on someone from ~ubuntu-sru to reject or accept the upload. ** Changed in: dpkg (Ubuntu Xenial) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: dpkg (Ubuntu Xenial) Status: In Progress => Incomplete ** Changed in: dpkg (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1842947 Title: dpkg 1.19.0.5ubuntu2.2 build did not recreate 'configure' file, losing changes in 'configure.ac' Status in dpkg package in Ubuntu: Fix Released Status in dpkg source package in Xenial: Incomplete Status in dpkg source package in Bionic: Fix Released Status in dpkg source package in Disco: Won't Fix Status in dpkg source package in Eoan: Fix Released Status in dpkg package in Debian: Fix Committed Bug description: [impact] dpkg at version 1.19.0.5ubuntu2 had support for zstd added: https://launchpad.net/ubuntu/+source/dpkg/1.19.0.5ubuntu2 part of that change was to update the 'configure.ac' file with zstd support, e.g.: http://launchpadlibrarian.net/366237303/dpkg_1.19.0.5ubuntu1_1.19.0.5ubuntu2.diff.gz note that the 'configure' file was not updated - which *should* be ok, as it should be recreated from the 'configure.ac' file during build. For the build of that version and the next (1.19.0.5ubuntu2.1), the 'configure' file was correctly recreated during build. However at version 1.19.0.5ubuntu2.2, the 'configure' file was not recreated during build. Thus, dpkg was not built linked against libzstd. This regresses the ability of dpkg to uncompress zstd-compressed packages, unless the zstd utility is installed on the local system. Since dpkg does not list the zstd package as a dep, it may not be installed on all users' systems who want to install a zstd-compressed package. [test case] on bionic system: $ sudo apt install ubuntu-dev-tools $ pull-lp-source dpkg 1.19.0.5ubuntu2.2 $ cd dpkg-1.19.0.5ubuntu2.2/ $ sudo apt build-dep . $ dpkg-buildpackage and verify if dpkg-deb is linked against libzstd: $ ldd build-tree/dpkg-deb/dpkg-deb | grep zstd or extract it from the deb itself and check: $ dpkg-deb -x ../dpkg_1.19.0.5ubuntu2.2_amd64.deb ../deb-files $ ldd ../deb-files/usr/bin/dpkg-deb | grep zstd simply touching the 'configure.ac' file (to bring its timestamp newer than the 'configure' file) causes the build to work correctly: $ mkdir no-touch $ cd no-touch $ dpkg-source -x ~/dpkg_1.19.0.5ubuntu2.2.dsc $ cd dpkg-1.19.0.5ubuntu2.2/ $ dpkg-buildpackage $ ldd build-tree/dpkg-deb/dpkg-deb | grep zstd $ $ mkdir touch $ cd touch $ dpkg-source -x ~/dpkg_1.19.0.5ubuntu2.2.dsc $ cd dpkg-1.19.0.5ubuntu2.2/ $ touch configure.ac $ dpkg-buildpackage $ ldd build-tree/dpkg-deb/dpkg-deb | grep zstd libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 (0x7f8c1d8af000) [regression potential] this forces autoreconf to be run for each build, which may add some small amount of time to the build. Other than that, the regression potential seems small, since autoreconf should be getting run for each build, and was for most (but not all) builds. Any regression would almost certainly involve a failure to build the package, or a failure to pick up new configure.ac changes correctly. [other info] this might not be an issue specifically with dpkg itself, it could be an issue with debhelper and other tooling that is responsible for calling autoconf or autoreconf during build. Or possibly a problem with the dpkg debian/rules or other related build config. Or, simply including the 'configure' file in the package source might be considered a bug, since it's an intermediate build file that really shouldn't be included. However, it's included in many source packages, including in debian, and removing it from all of them seems unlikely and/or unwieldy. Additionally, for "normal" packages that use quilt (i.e., aren't native), any changes to the 'configure.ac' file would be done with a patch, meaning the pre-build process would always make the 'configure.ac' file newer than the 'configure' file. Maybe for native packages, autoconf/autoreconf should always be called with -f, or maybe the 'configure' file should be removed from native packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1842947/+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 1869453] [NEW] Move gvnic driver from -modules-extras to -modules
Public bug reported: There's a salesforce ticket that I will link to here. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: Fix Committed ** Affects: linux-gcp (Ubuntu Disco) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-gcp (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Bionic) Status: New => Fix Committed ** No longer affects: linux-gcp (Ubuntu Disco) ** Also affects: linux-gcp (Ubuntu Disco) 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/1869453 Title: Move gvnic driver from -modules-extras to -modules Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Xenial: New Status in linux-gcp source package in Bionic: Fix Committed Status in linux-gcp source package in Disco: New Status in linux-gcp source package in Eoan: New Status in linux-gcp source package in Focal: New Bug description: There's a salesforce ticket that I will link to here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1869453/+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 1869453] Re: Move gvnic driver from -modules-extras to -modules
** Changed in: linux-gcp (Ubuntu Xenial) Status: New => Fix Committed ** No longer affects: linux-gcp (Ubuntu Disco) ** Changed in: linux-gcp (Ubuntu Eoan) Status: New => Fix Committed -- 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/1869453 Title: Move gvnic driver from -modules-extras to -modules Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Xenial: Fix Committed Status in linux-gcp source package in Bionic: Fix Committed Status in linux-gcp source package in Eoan: Fix Committed Status in linux-gcp source package in Focal: New Bug description: There's a salesforce ticket that I will link to here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1869453/+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 1860813] Re: LXC container reports spike in swap occasionally
** Also affects: lxcfs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lxcfs (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: lxcfs (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: lxcfs (Ubuntu Bionic) Assignee: (unassigned) => Kellen Renshaw (krenshaw) ** Changed in: lxcfs (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: lxcfs (Ubuntu Bionic) Status: New => In Progress ** Tags added: sts-sponsor-slashd -- 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/1860813 Title: LXC container reports spike in swap occasionally Status in lxcfs package in Ubuntu: Fix Released Status in lxcfs source package in Xenial: New Status in lxcfs source package in Bionic: In Progress Status in lxcfs source package in Eoan: New Bug description: [Impact] * lxcfs provides a container-specific view of /proc/meminfo. Occasionally, with near zero or zero swap usage *and* swap accounting turned on (kernel parameter swapaccount=1), the container will report 100% swap utilization. * This issue has been encountered and could result in unecessary alerts or potential automated attempts at remediating a non-existent "full swap" issue. * This fix changed the logic used for SwapFree when swap accounting is enabled to better handle situations where memswusage is less than memusage, caused by the fuzziness of the usage_in_bytes counters used as the source. Specifically, it added a check for memusage being larger than memswusage and if so, sets 0 as the value of swapusage. Otherwise the calculation (memswusage - memusage) remains the same. [Test Case] * Requires a Bionic (18.04) or Eoan (19.10) host with swap space. * Enable swap accounting with the "swapaccount=1" kernel parameter on the kernel command line. Edit /etc/default/grub, add "swapaccount=1" to the GRUB_CMDLINE_LINUX_DEFAULT="other parameters" line, then run "update-grub" and reboot to make the change active. * Ensure lxd is installed, "sudo apt install lxd" * Create a lxd/lxc container with "lxc launch ubuntu:X container_name" with X being either b[ionic] or e[oan]. * Open two shells to the container with "lxc shell container_name" * In one of the shells, run: watch -n 0.1 "grep Swap /proc/meminfo" * In the other, run: while true; do free; done * You should see SwapFree intermittently drop to zero in the first terminal. * The fix results in small non-zero swap "usage" intermittently instead of intermittent SwapFree = 0. [Regression Potential] * Low, as swap accounting must be enabled to encounter the bug and the fix. * Potential for unanticipated edge cases in the values of memusage and memswusage to cause incorrect swap reporting within the container, with swap accounting turned on. * Any tooling that expected, compensated, or relied on the behavior may no longer work as expected. [Other Info] * Cherrypick of a one line fix to address this specific situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1860813/+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
