[Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

2024-07-11 Thread Alberto 
Unfortunately this requested change has introduced severe issues with
the kernels in which it was applied, by breaking compatibility with the
32bit glibc.

Even if an application is built with _TIME_BITS=64, and therefore the
application has no year 2038 issues, glibc itself will use the 32bit
time syscalls when there is no deadline or when the deadline fits in the
32bit syscall.

See, apart from the issue linked above, these which provide more details:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2071445
https://github.com/actions/runner-images/issues/9977

Please note that it is quite normal to build and run 32bit applications
in 64bit systems, and that it is the base for a lot of CI/test setups.


** Bug watch added: github.com/actions/runner-images/issues #9977
   https://github.com/actions/runner-images/issues/9977

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

Title:
  Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

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


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

[Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

2024-05-31 Thread Simon Déziel 
Disabling support for 32bit time caught some by surprise:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2062176

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

Title:
  Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

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


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

[Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

2024-05-14 Thread Ubuntu Kernel Bot 
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the
problem still exists, change the tag 'verification-needed-jammy-linux-
nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-6.8-v2 
verification-needed-jammy-linux-nvidia-6.8

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

Title:
  Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

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


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

[Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

2024-04-03 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux-raspi - 6.8.0-1002.2

---
linux-raspi (6.8.0-1002.2) noble; urgency=medium

  * noble/linux-raspi: 6.8.0-1002.2 -proposed tracker (LP: #2057941)

  * Wifi wlan0 device not present on Raspberry Pi 3A+ (LP: #2056635)
- [Config] raspi: Set MMC_BCM2835_SDHOST=y

  * Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives) (LP: #2038582)
- [Config] raspi: Set COMPAT_32BIT_TIME=n

  * Miscellaneous Ubuntu changes
- [Config] raspi: updateconfigs after update to raspberrypi rpi-6.8.y
  (2024-03-14)

  * Miscellaneous upstream changes
- dtoverlays: Correct width/height on Waveshare 2.8" panel
- dtoverlays: rotate override needs to update "rotation" for drm mode
- configs: Disable process/register dumps via SysRq
- ASOc: Add HiFiBerry DAC8X to the simple card driver
- Overlays: Add definitions for HiFiBerry 8 channel DAC8X
- drm: Add DRM_MODE_TV_MODE_MONOCHROME
- drm/vc4: Add monochrome mode to the VEC.
- media: i2c: imx296: Updated register setting to fix Fast Trigger
- dt-bindings: add additional RP1 PLL output channels
- drivers: clk: rp1: add GPCLK source muxes and additional PLL dividers
- DT: rp1: add general-purpose clock source definitions
- drivers: clk: rp1: constrain clock divider outputs to design maximums
- vc4: Add jack detection to HDMI audio driver
- fixup! ASoC: dwc: Defer bclk_ratio handling to hw_params
- ASoC: bcm: Use the correct sample width value
- clk: rp1: Reserve pll_audio* for clk_i2s
- clk: rp1: Allow clk_i2s to change the audio PLLs
- regulator: Add a regulator for the new LCD panels
- dt-bindings: ili9881c: add compatible string for new panels
- drm/panel: ilitek-ili9881c: Allow configuration of the number of lanes
- drm/panel: ili9881: Add configuration for the new panels
- defconfigs: Add panel regulator to all the Pi defconfigs
- dtoverlays: Add overlays for 5" and 7" ILI9881 panels
- ARM: dts: bcm2712-rpi: Add i2c_pins labels
- ASoC: dwc: Correct channel count reporting
- Driver:add waveshare 4inch dsi lcd (C) driver
- Dtoverlay:add waveshare 4inch dsi lcd (C) dtoverlay
- Dtoverlay:fix waveshare 11.9inch touch orientation error
- Dtoverlay:Add waveshare 4inch dsi lcd (C) parameters to the README

  [ Ubuntu: 6.8.0-20.20 ]

  * noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
  * Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set
- Documentation/hw-vuln: Add documentation for RFDS
- x86/rfds: Mitigate Register File Data Sampling (RFDS)
- KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests
- Linux 6.8.1
  * Autopkgtest failures on amd64 (LP: #2048768)
- [Packaging] update to clang-18
  * Miscellaneous Ubuntu changes
- SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with
  CONFIG_SECURITY=n
- [Config] amd64: MITIGATION_RFDS=y

  [ Ubuntu: 6.8.0-19.19 ]

  * noble/linux: 6.8.0-19.19 -proposed tracker (LP: #2057910)
  * Miscellaneous Ubuntu changes
- [Packaging] re-introduce linux-doc as an empty package

  [ Ubuntu: 6.8.0-18.18 ]

  * noble/linux: 6.8.0-18.18 -proposed tracker (LP: #2057456)
  * Miscellaneous Ubuntu changes
- [Packaging] drop dependency on libclang-17

  [ Ubuntu: 6.8.0-17.17 ]

  * noble/linux: 6.8.0-17.17 -proposed tracker (LP: #2056745)
  * Miscellaneous upstream changes
- Revert "UBUNTU: [Packaging] Add debian/control sanity check"

  [ Ubuntu: 6.8.0-16.16 ]

  * noble/linux: 6.8.0-16.16 -proposed tracker (LP: #2056738)
  * left-over ceph debugging printks (LP: #2056616)
- Revert "UBUNTU: SAUCE: ceph: make sure all the files successfully put 
before
  unmounting"
  * qat: Improve error recovery flows (LP: #2056354)
- crypto: qat - add heartbeat error simulator
- crypto: qat - disable arbitration before reset
- crypto: qat - update PFVF protocol for recovery
- crypto: qat - re-enable sriov after pf reset
- crypto: qat - add fatal error notification
- crypto: qat - add auto reset on error
- crypto: qat - limit heartbeat notifications
- crypto: qat - improve aer error reset handling
- crypto: qat - change SLAs cleanup flow at shutdown
- crypto: qat - resolve race condition during AER recovery
- Documentation: qat: fix auto_reset section
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate
  ima_filter_rule from security_audit_rule
- SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure
  management of the sock security
- SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data
  structure.
- SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label 
collisions
  with stacked LSMs
- SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use

[Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

2024-03-02 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux-azure - 6.8.0-1001.1

---
linux-azure (6.8.0-1001.1) noble; urgency=medium

  * noble/linux-azure: 6.8.0-1001.1 -proposed tracker (LP: #2052777)

  * Packaging resync (LP: #1786013)
- debian.azure/dkms-versions -- update from kernel-versions 
(main/d2024.02.07)

  * Azure: cifs modules missing from the linux-modules package (LP: #2052980)
- [Config] Move cifs.ko to linux-modules package

  * Azure: Enable CONFIG_TEST_LOCKUP (LP: #2052723)
- [Config] CONFIG_TEST_LOCKUP=m

  * Miscellaneous Ubuntu changes
- [Packaging] azure: update Rust toolchain
- [Packaging] azure: move to kernel v6.8
- [Config] azure: update annotations after moving to v6.8

  [ Ubuntu: 6.8.0-9.9 ]

  * noble/linux: 6.8.0-9.9 -proposed tracker (LP: #2052945)
  * Miscellaneous upstream changes
- Revert "UBUNTU: [Packaging] temporarily disable Rust dependencies on
  riscv64"

  [ Ubuntu: 6.8.0-8.8 ]

  * noble/linux: 6.8.0-8.8 -proposed tracker (LP: #2052918)
  * Miscellaneous Ubuntu changes
- [Packaging] riscv64: enable linux-libc-dev build
- v6.8-rc4 rebase
  * Rebase on v6.8-rc4

  [ Ubuntu: 6.8.0-7.7 ]

  * noble/linux: 6.8.0-7.7 -proposed tracker (LP: #2052691)
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate
  ima_filter_rule from security_audit_rule
- SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure
  management of the sock security
- SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data
  structure.
- SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label 
collisions
  with stacked LSMs
- SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use lsmblob in
  security_audit_rule_match
- SAUCE: apparmor4.0.0 [06/87]: LSM stacking v39: LSM: Add lsmblob_to_secctx
  hook
- SAUCE: apparmor4.0.0 [07/87]: LSM stacking v39: Audit: maintain an lsmblob
  in audit_context
- SAUCE: apparmor4.0.0 [08/87]: LSM stacking v39: LSM: Use lsmblob in
  security_ipc_getsecid
- SAUCE: apparmor4.0.0 [09/87]: LSM stacking v39: Audit: Update shutdown LSM
  data
- SAUCE: apparmor4.0.0 [10/87]: LSM stacking v39: LSM: Use lsmblob in
  security_current_getsecid
- SAUCE: apparmor4.0.0 [11/87]: LSM stacking v39: LSM: Use lsmblob in
  security_inode_getsecid
- SAUCE: apparmor4.0.0 [12/87]: LSM stacking v39: Audit: use an lsmblob in
  audit_names
- SAUCE: apparmor4.0.0 [13/87]: LSM stacking v39: LSM: Create new
  security_cred_getlsmblob LSM hook
- SAUCE: apparmor4.0.0 [14/87]: LSM stacking v39: Audit: Change context data
  from secid to lsmblob
- SAUCE: apparmor4.0.0 [15/87]: LSM stacking v39: Netlabel: Use lsmblob for
  audit data
- SAUCE: apparmor4.0.0 [16/87]: LSM stacking v39: LSM: Ensure the correct 
LSM
  context releaser
- SAUCE: apparmor4.0.0 [17/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [18/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [19/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [20/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [21/87]: LSM stacking v39: LSM:
  security_lsmblob_to_secctx module selection
- SAUCE: apparmor4.0.0 [22/87]: LSM stacking v39: Audit: Create audit_stamp
  structure
- SAUCE: apparmor4.0.0 [23/87]: LSM stacking v39: Audit: Allow multiple
  records in an audit_buffer
- SAUCE: apparmor4.0.0 [24/87]: LSM stacking v39: Audit: Add record for
  multiple task security contexts
- SAUCE: apparmor4.0.0 [25/87]: LSM stacking v39: audit: multiple subject 
lsm
  values for netlabel
- SAUCE: apparmor4.0.0 [26/87]: LSM stacking v39: Audit: Add record for
  multiple object contexts
- SAUCE: apparmor4.0.0 [27/87]: LSM stacking v39: LSM: Remove unused
  lsmcontext_init()
- SAUCE: apparmor4.0.0 [28/87]: LSM stacking v39: LSM: Improve logic in
  security_getprocattr
- SAUCE: apparmor4.0.0 [29/87]: LSM stacking v39: LSM: secctx provider check
  on release
- SAUCE: apparmor4.0.0 [31/87]: LSM stacking v39: LSM: Exclusive secmark 
usage
- SAUCE: apparmor4.0.0 [32/87]: LSM stacking v39: LSM: Identify which LSM
  handles the context string
- SAUCE: apparmor4.0.0 [33/87]: LSM stacking v39: AppArmor: Remove the
  exclusive flag
- SAUCE: apparmor4.0.0 [34/87]: LSM stacking v39: LSM: Add mount opts blob
  size tracking
- SAUCE: apparmor4.0.0 [35/87]: LSM stacking v39: LSM: allocate mnt_opts 
blobs
  instead of module specific data
- SAUCE: apparmor4.0.0 [36/87]: LSM stacking v39: LSM: Infrastructure
  management of the key security blob
- SAUCE:

[Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

2024-03-02 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux-aws - 6.8.0-1001.1

---
linux-aws (6.8.0-1001.1) noble; urgency=medium

  * noble/linux-aws: 6.8.0-1001.1 -proposed tracker (LP: #2052774)

  * Packaging resync (LP: #1786013)
- debian.aws/dkms-versions -- update from kernel-versions (main/d2024.02.07)

  * AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64 (LP: #2045428)
- Revert "UBUNTU: SAUCE: net: ena: fix too long default tx interrupt
  moderation interval"

  * Miscellaneous Ubuntu changes
- [Packaging] remove custom ABI/retpoline check files
- [Config] update annotations after rebase to v6.8

  [ Ubuntu: 6.8.0-7.7 ]

  * noble/linux: 6.8.0-7.7 -proposed tracker (LP: #2052691)
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate
  ima_filter_rule from security_audit_rule
- SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure
  management of the sock security
- SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data
  structure.
- SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label 
collisions
  with stacked LSMs
- SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use lsmblob in
  security_audit_rule_match
- SAUCE: apparmor4.0.0 [06/87]: LSM stacking v39: LSM: Add lsmblob_to_secctx
  hook
- SAUCE: apparmor4.0.0 [07/87]: LSM stacking v39: Audit: maintain an lsmblob
  in audit_context
- SAUCE: apparmor4.0.0 [08/87]: LSM stacking v39: LSM: Use lsmblob in
  security_ipc_getsecid
- SAUCE: apparmor4.0.0 [09/87]: LSM stacking v39: Audit: Update shutdown LSM
  data
- SAUCE: apparmor4.0.0 [10/87]: LSM stacking v39: LSM: Use lsmblob in
  security_current_getsecid
- SAUCE: apparmor4.0.0 [11/87]: LSM stacking v39: LSM: Use lsmblob in
  security_inode_getsecid
- SAUCE: apparmor4.0.0 [12/87]: LSM stacking v39: Audit: use an lsmblob in
  audit_names
- SAUCE: apparmor4.0.0 [13/87]: LSM stacking v39: LSM: Create new
  security_cred_getlsmblob LSM hook
- SAUCE: apparmor4.0.0 [14/87]: LSM stacking v39: Audit: Change context data
  from secid to lsmblob
- SAUCE: apparmor4.0.0 [15/87]: LSM stacking v39: Netlabel: Use lsmblob for
  audit data
- SAUCE: apparmor4.0.0 [16/87]: LSM stacking v39: LSM: Ensure the correct 
LSM
  context releaser
- SAUCE: apparmor4.0.0 [17/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [18/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [19/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [20/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [21/87]: LSM stacking v39: LSM:
  security_lsmblob_to_secctx module selection
- SAUCE: apparmor4.0.0 [22/87]: LSM stacking v39: Audit: Create audit_stamp
  structure
- SAUCE: apparmor4.0.0 [23/87]: LSM stacking v39: Audit: Allow multiple
  records in an audit_buffer
- SAUCE: apparmor4.0.0 [24/87]: LSM stacking v39: Audit: Add record for
  multiple task security contexts
- SAUCE: apparmor4.0.0 [25/87]: LSM stacking v39: audit: multiple subject 
lsm
  values for netlabel
- SAUCE: apparmor4.0.0 [26/87]: LSM stacking v39: Audit: Add record for
  multiple object contexts
- SAUCE: apparmor4.0.0 [27/87]: LSM stacking v39: LSM: Remove unused
  lsmcontext_init()
- SAUCE: apparmor4.0.0 [28/87]: LSM stacking v39: LSM: Improve logic in
  security_getprocattr
- SAUCE: apparmor4.0.0 [29/87]: LSM stacking v39: LSM: secctx provider check
  on release
- SAUCE: apparmor4.0.0 [31/87]: LSM stacking v39: LSM: Exclusive secmark 
usage
- SAUCE: apparmor4.0.0 [32/87]: LSM stacking v39: LSM: Identify which LSM
  handles the context string
- SAUCE: apparmor4.0.0 [33/87]: LSM stacking v39: AppArmor: Remove the
  exclusive flag
- SAUCE: apparmor4.0.0 [34/87]: LSM stacking v39: LSM: Add mount opts blob
  size tracking
- SAUCE: apparmor4.0.0 [35/87]: LSM stacking v39: LSM: allocate mnt_opts 
blobs
  instead of module specific data
- SAUCE: apparmor4.0.0 [36/87]: LSM stacking v39: LSM: Infrastructure
  management of the key security blob
- SAUCE: apparmor4.0.0 [37/87]: LSM stacking v39: LSM: Infrastructure
  management of the mnt_opts security blob
- SAUCE: apparmor4.0.0 [38/87]: LSM stacking v39: LSM: Correct handling of
  ENOSYS in inode_setxattr
- SAUCE: apparmor4.0.0 [39/87]: LSM stacking v39: LSM: Remove lsmblob
  scaffolding
- SAUCE: apparmor4.0.0 [40/87]: LSM stacking v39: LSM: Allow reservation of
  netlabel
- SAUCE: apparmor4.0.0 [41/87]: LSM stacking v39: LSM: restrict
  security_cred_getsecid() to a single LSM
- SAUCE:

[Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

2024-03-02 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux-gcp - 6.8.0-1002.2

---
linux-gcp (6.8.0-1002.2) noble; urgency=medium

  * noble/linux-gcp: 6.8.0-1002.2 -proposed tracker (LP: #2053032)

  * Miscellaneous Ubuntu changes
- [packaging] update rust, clang and bindgen build-deps
- [Packaging] add Rust build deps for riscv64

 -- Paolo Pisati   Tue, 13 Feb 2024 16:15:29
+0100

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

Title:
  Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

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


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

[Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

2024-03-02 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux-oracle - 6.8.0-1001.1

---
linux-oracle (6.8.0-1001.1) noble; urgency=medium

  * noble/linux-oracle: 6.8.0-1001.1 -proposed tracker (LP: #2052776)

  * Packaging resync (LP: #1786013)
- debian.oracle/dkms-versions -- update from kernel-versions
  (main/d2024.02.07)

  * [arm64] Increase max CPU count to 512 (LP: #2046184)
- [Config]: oracle: Increase max CPU count to 512

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs following 6.8.0-7.7 rebase

  [ Ubuntu: 6.8.0-7.7 ]

  * noble/linux: 6.8.0-7.7 -proposed tracker (LP: #2052691)
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate
  ima_filter_rule from security_audit_rule
- SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure
  management of the sock security
- SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data
  structure.
- SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label 
collisions
  with stacked LSMs
- SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use lsmblob in
  security_audit_rule_match
- SAUCE: apparmor4.0.0 [06/87]: LSM stacking v39: LSM: Add lsmblob_to_secctx
  hook
- SAUCE: apparmor4.0.0 [07/87]: LSM stacking v39: Audit: maintain an lsmblob
  in audit_context
- SAUCE: apparmor4.0.0 [08/87]: LSM stacking v39: LSM: Use lsmblob in
  security_ipc_getsecid
- SAUCE: apparmor4.0.0 [09/87]: LSM stacking v39: Audit: Update shutdown LSM
  data
- SAUCE: apparmor4.0.0 [10/87]: LSM stacking v39: LSM: Use lsmblob in
  security_current_getsecid
- SAUCE: apparmor4.0.0 [11/87]: LSM stacking v39: LSM: Use lsmblob in
  security_inode_getsecid
- SAUCE: apparmor4.0.0 [12/87]: LSM stacking v39: Audit: use an lsmblob in
  audit_names
- SAUCE: apparmor4.0.0 [13/87]: LSM stacking v39: LSM: Create new
  security_cred_getlsmblob LSM hook
- SAUCE: apparmor4.0.0 [14/87]: LSM stacking v39: Audit: Change context data
  from secid to lsmblob
- SAUCE: apparmor4.0.0 [15/87]: LSM stacking v39: Netlabel: Use lsmblob for
  audit data
- SAUCE: apparmor4.0.0 [16/87]: LSM stacking v39: LSM: Ensure the correct 
LSM
  context releaser
- SAUCE: apparmor4.0.0 [17/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [18/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [19/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [20/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [21/87]: LSM stacking v39: LSM:
  security_lsmblob_to_secctx module selection
- SAUCE: apparmor4.0.0 [22/87]: LSM stacking v39: Audit: Create audit_stamp
  structure
- SAUCE: apparmor4.0.0 [23/87]: LSM stacking v39: Audit: Allow multiple
  records in an audit_buffer
- SAUCE: apparmor4.0.0 [24/87]: LSM stacking v39: Audit: Add record for
  multiple task security contexts
- SAUCE: apparmor4.0.0 [25/87]: LSM stacking v39: audit: multiple subject 
lsm
  values for netlabel
- SAUCE: apparmor4.0.0 [26/87]: LSM stacking v39: Audit: Add record for
  multiple object contexts
- SAUCE: apparmor4.0.0 [27/87]: LSM stacking v39: LSM: Remove unused
  lsmcontext_init()
- SAUCE: apparmor4.0.0 [28/87]: LSM stacking v39: LSM: Improve logic in
  security_getprocattr
- SAUCE: apparmor4.0.0 [29/87]: LSM stacking v39: LSM: secctx provider check
  on release
- SAUCE: apparmor4.0.0 [31/87]: LSM stacking v39: LSM: Exclusive secmark 
usage
- SAUCE: apparmor4.0.0 [32/87]: LSM stacking v39: LSM: Identify which LSM
  handles the context string
- SAUCE: apparmor4.0.0 [33/87]: LSM stacking v39: AppArmor: Remove the
  exclusive flag
- SAUCE: apparmor4.0.0 [34/87]: LSM stacking v39: LSM: Add mount opts blob
  size tracking
- SAUCE: apparmor4.0.0 [35/87]: LSM stacking v39: LSM: allocate mnt_opts 
blobs
  instead of module specific data
- SAUCE: apparmor4.0.0 [36/87]: LSM stacking v39: LSM: Infrastructure
  management of the key security blob
- SAUCE: apparmor4.0.0 [37/87]: LSM stacking v39: LSM: Infrastructure
  management of the mnt_opts security blob
- SAUCE: apparmor4.0.0 [38/87]: LSM stacking v39: LSM: Correct handling of
  ENOSYS in inode_setxattr
- SAUCE: apparmor4.0.0 [39/87]: LSM stacking v39: LSM: Remove lsmblob
  scaffolding
- SAUCE: apparmor4.0.0 [40/87]: LSM stacking v39: LSM: Allow reservation of
  netlabel
- SAUCE: apparmor4.0.0 [41/87]: LSM stacking v39: LSM: restrict
  security_cred_getsecid() to a single LSM
- SAUCE: apparmor4.0.0 [42/87]: LSM stacking v39: Smack: Remove
  LSM_FLAG_EXCLUSIVE
- SAUCE:

[Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

2024-03-02 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 6.8.0-11.11

---
linux (6.8.0-11.11) noble; urgency=medium

  * noble/linux: 6.8.0-11.11 -proposed tracker (LP: #2053094)

  * Miscellaneous Ubuntu changes
- [Packaging] riscv64: disable building unnecessary binary debs

 -- Paolo Pisati   Wed, 14 Feb 2024 00:04:31
+0100

** Changed in: linux-gcp (Ubuntu)
   Status: New => Fix Released

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

Title:
  Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

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


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