[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2020-01-07 Thread Po-Hsu Lin
** Changed in: ubuntu-kernel-tests
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-12-06 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.3.0-24.26

---
linux (5.3.0-24.26) eoan; urgency=medium

  * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)

  * Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- dm snapshot: introduce account_start_copy() and account_end_copy()
- dm snapshot: rework COW throttling to fix deadlock
- Btrfs: fix inode cache block reserve leak on failure to allocate data 
space
- btrfs: qgroup: Always free PREALLOC META reserve in
  btrfs_delalloc_release_extents()
- iio: adc: meson_saradc: Fix memory allocation order
- iio: fix center temperature of bmc150-accel-core
- libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature
- perf tests: Avoid raising SEGV using an obvious NULL dereference
- perf map: Fix overlapped map handling
- perf script brstackinsn: Fix recovery from LBR/binary mismatch
- perf jevents: Fix period for Intel fixed counters
- perf tools: Propagate get_cpuid() error
- perf annotate: Propagate perf_env__arch() error
- perf annotate: Fix the signedness of failure returns
- perf annotate: Propagate the symbol__annotate() error return
- perf annotate: Fix arch specific ->init() failure errors
- perf annotate: Return appropriate error code for allocation failures
- perf annotate: Don't return -1 for error when doing BPF disassembly
- staging: rtl8188eu: fix null dereference when kzalloc fails
- RDMA/siw: Fix serialization issue in write_space()
- RDMA/hfi1: Prevent memory leak in sdma_init
- RDMA/iw_cxgb4: fix SRQ access from dump_qp()
- RDMA/iwcm: Fix a lock inversion issue
- HID: hyperv: Use in-place iterator API in the channel callback
- kselftest: exclude failed TARGETS from runlist
- selftests/kselftest/runner.sh: Add 45 second timeout per test
- nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request
- arm64: cpufeature: Effectively expose FRINT capability to userspace
- arm64: Fix incorrect irqflag restore for priority masking for compat
- arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 
#1542419
- tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()'
- tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()'
- serial/sifive: select SERIAL_EARLYCON
- tty: n_hdlc: fix build on SPARC
- misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach
- RDMA/core: Fix an error handling path in 'res_get_common_doit()'
- RDMA/cm: Fix memory leak in cm_add/remove_one
- RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path
- RDMA/mlx5: Do not allow rereg of a ODP MR
- RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu
- RDMA/mlx5: Add missing synchronize_srcu() for MW cases
- gpio: max77620: Use correct unit for debounce times
- fs: cifs: mute -Wunused-const-variable message
- arm64: vdso32: Fix broken compat vDSO build warnings
- arm64: vdso32: Detect binutils support for dmb ishld
- serial: mctrl_gpio: Check for NULL pointer
- serial: 8250_omap: Fix gpio check for auto RTS/CTS
- arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG
- arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally
- efi/cper: Fix endianness of PCIe class code
- efi/x86: Do not clean dummy variable in kexec path
- MIPS: include: Mark __cmpxchg as __always_inline
- riscv: avoid kernel hangs when trapped in BUG()
- riscv: avoid sending a SIGTRAP to a user thread trapped in WARN()
- riscv: Correct the handling of unexpected ebreak in do_trap_break()
- x86/xen: Return from panic notifier
- ocfs2: clear zero in unaligned direct IO
- fs: ocfs2: fix possible null-pointer dereferences in
  ocfs2_xa_prepare_entry()
- fs: ocfs2: fix a possible null-pointer dereference in
  ocfs2_write_end_nolock()
- fs: ocfs2: fix a possible null-pointer dereference in
  ocfs2_info_scan_inode_alloc()
- btrfs: silence maybe-uninitialized warning in clone_range
- arm64: armv8_deprecated: Checking return value for memory allocation
- sched/fair: Scale bandwidth quota and period without losing quota/period
  ratio precision
- sched/vtime: Fix guest/system mis-accounting on task switch
- perf/core: Rework memory accounting in perf_mmap()
- perf/core: Fix corner case in perf_rotate_context()
- perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp
- drm/amdgpu: fix memory leak
- iio: imu: adis16400: release allocated memory on failure
- iio: imu: adis16400: fix memory leak
- iio: imu: st_lsm6dsx: fix waitime for st_lsm6dsx i2c controller
- MIPS: include: Mark __xchg as __always_inline
- MIPS: fw: sni: Fix out of bounds init of o32 stack
- s390/cio: fix virtio-ccw DMA without PV
- virt: vbox: fix memory 

[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-12-02 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.3.0-24.26

---
linux (5.3.0-24.26) eoan; urgency=medium

  * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)

  * Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- dm snapshot: introduce account_start_copy() and account_end_copy()
- dm snapshot: rework COW throttling to fix deadlock
- Btrfs: fix inode cache block reserve leak on failure to allocate data 
space
- btrfs: qgroup: Always free PREALLOC META reserve in
  btrfs_delalloc_release_extents()
- iio: adc: meson_saradc: Fix memory allocation order
- iio: fix center temperature of bmc150-accel-core
- libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature
- perf tests: Avoid raising SEGV using an obvious NULL dereference
- perf map: Fix overlapped map handling
- perf script brstackinsn: Fix recovery from LBR/binary mismatch
- perf jevents: Fix period for Intel fixed counters
- perf tools: Propagate get_cpuid() error
- perf annotate: Propagate perf_env__arch() error
- perf annotate: Fix the signedness of failure returns
- perf annotate: Propagate the symbol__annotate() error return
- perf annotate: Fix arch specific ->init() failure errors
- perf annotate: Return appropriate error code for allocation failures
- perf annotate: Don't return -1 for error when doing BPF disassembly
- staging: rtl8188eu: fix null dereference when kzalloc fails
- RDMA/siw: Fix serialization issue in write_space()
- RDMA/hfi1: Prevent memory leak in sdma_init
- RDMA/iw_cxgb4: fix SRQ access from dump_qp()
- RDMA/iwcm: Fix a lock inversion issue
- HID: hyperv: Use in-place iterator API in the channel callback
- kselftest: exclude failed TARGETS from runlist
- selftests/kselftest/runner.sh: Add 45 second timeout per test
- nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request
- arm64: cpufeature: Effectively expose FRINT capability to userspace
- arm64: Fix incorrect irqflag restore for priority masking for compat
- arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 
#1542419
- tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()'
- tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()'
- serial/sifive: select SERIAL_EARLYCON
- tty: n_hdlc: fix build on SPARC
- misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach
- RDMA/core: Fix an error handling path in 'res_get_common_doit()'
- RDMA/cm: Fix memory leak in cm_add/remove_one
- RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path
- RDMA/mlx5: Do not allow rereg of a ODP MR
- RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu
- RDMA/mlx5: Add missing synchronize_srcu() for MW cases
- gpio: max77620: Use correct unit for debounce times
- fs: cifs: mute -Wunused-const-variable message
- arm64: vdso32: Fix broken compat vDSO build warnings
- arm64: vdso32: Detect binutils support for dmb ishld
- serial: mctrl_gpio: Check for NULL pointer
- serial: 8250_omap: Fix gpio check for auto RTS/CTS
- arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG
- arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally
- efi/cper: Fix endianness of PCIe class code
- efi/x86: Do not clean dummy variable in kexec path
- MIPS: include: Mark __cmpxchg as __always_inline
- riscv: avoid kernel hangs when trapped in BUG()
- riscv: avoid sending a SIGTRAP to a user thread trapped in WARN()
- riscv: Correct the handling of unexpected ebreak in do_trap_break()
- x86/xen: Return from panic notifier
- ocfs2: clear zero in unaligned direct IO
- fs: ocfs2: fix possible null-pointer dereferences in
  ocfs2_xa_prepare_entry()
- fs: ocfs2: fix a possible null-pointer dereference in
  ocfs2_write_end_nolock()
- fs: ocfs2: fix a possible null-pointer dereference in
  ocfs2_info_scan_inode_alloc()
- btrfs: silence maybe-uninitialized warning in clone_range
- arm64: armv8_deprecated: Checking return value for memory allocation
- sched/fair: Scale bandwidth quota and period without losing quota/period
  ratio precision
- sched/vtime: Fix guest/system mis-accounting on task switch
- perf/core: Rework memory accounting in perf_mmap()
- perf/core: Fix corner case in perf_rotate_context()
- perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp
- drm/amdgpu: fix memory leak
- iio: imu: adis16400: release allocated memory on failure
- iio: imu: adis16400: fix memory leak
- iio: imu: st_lsm6dsx: fix waitime for st_lsm6dsx i2c controller
- MIPS: include: Mark __xchg as __always_inline
- MIPS: fw: sni: Fix out of bounds init of o32 stack
- s390/cio: fix virtio-ccw DMA without PV
- virt: vbox: fix memory 

[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-12-02 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.0.0-37.40

---
linux (5.0.0-37.40) disco; urgency=medium

  * disco/linux: 5.0.0-37.40 -proposed tracker (LP: #1852253)

  * System hangs at early boot (LP: #1851216)
- x86/timer: Skip PIT initialization on modern chipsets

  * drm/i915: Add support for another CMP-H PCH (LP: #1848491)
- drm/i915/cml: Add second PCH ID for CMP

  * Some EFI systems fail to boot in efi_init() when booted via maas
(LP: #1851810)
- efi: efi_get_memory_map -- increase map headroom

  * seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test (LP: #1849281)
- SAUCE: seccomp: avoid overflow in implicit constant conversion
- SAUCE: seccomp: rework define for SECCOMP_USER_NOTIF_FLAG_CONTINUE
- SAUCE: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

  * dkms artifacts may expire from the pool (LP: #1850958)
- [Packaging] dkms -- try launchpad librarian for pool downloads
- [Packaging] dkms -- dkms-build quieten wget verbiage

  * update ENA driver to version 2.1.0 (LP: #1850175)
- net: ena: fix swapped parameters when calling
  ena_com_indirect_table_fill_entry
- net: ena: fix: Free napi resources when ena_up() fails
- net: ena: fix incorrect test of supported hash function
- net: ena: fix return value of ena_com_config_llq_info()
- net: ena: improve latency by disabling adaptive interrupt moderation by
  default
- net: ena: fix ena_com_fill_hash_function() implementation
- net: ena: add handling of llq max tx burst size
- net: ena: ethtool: add extra properties retrieval via get_priv_flags
- net: ena: replace free_tx/rx_ids union with single free_ids field in
  ena_ring
- net: ena: arrange ena_probe() function variables in reverse christmas tree
- net: ena: add newline at the end of pr_err prints
- net: ena: documentation: update ena.txt
- net: ena: allow automatic fallback to polling mode
- net: ena: add support for changing max_header_size in LLQ mode
- net: ena: optimise calculations for CQ doorbell
- net: ena: add good checksum counter
- net: ena: use dev_info_once instead of static variable
- net: ena: add MAX_QUEUES_EXT get feature admin command
- net: ena: enable negotiating larger Rx ring size
- net: ena: make ethtool show correct current and max queue sizes
- net: ena: allow queue allocation backoff when low on memory
- net: ena: add ethtool function for changing io queue sizes
- net: ena: remove inline keyword from functions in *.c
- net: ena: update driver version from 2.0.3 to 2.1.0
- net: ena: Fix bug where ring allocation backoff stopped too late
- Revert "net: ena: ethtool: add extra properties retrieval via
  get_priv_flags"
- net: ena: don't wake up tx queue when down
- net: ena: clean up indentation issue

  * Add Intel Comet Lake ethernet support (LP: #1848555)
- SAUCE: e1000e: Add support for Comet Lake

  * Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD
GEO_TX_POWER_LIMIT (LP: #1846016)
- iwlwifi: exclude GEO SAR support for 3168

  * tsc marked unstable after entered PC10 on Intel CoffeeLake (LP: #1840239)
- SAUCE: x86/intel: Disable HPET on Intel Coffe Lake platforms
- SAUCE: x86/intel: Disable HPET on Intel Ice Lake platforms

  * cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled
cloud (LP: #1848481)
- [Packaging] include iavf/i40evf in generic

  * High power consumption using 5.0.0-25-generic (LP: #1840835)
- PCI: Add a helper to check Power Resource Requirements _PR3 existence
- ALSA: hda: Allow HDA to be runtime suspended when dGPU is not bound to a
  driver
- PCI: Fix missing inline for pci_pr3_present()

  * CML CPUIDs (LP: #1843794)
- x86/cpu: Add Comet Lake to the Intel CPU models header

  * shiftfs: prevent exceeding project quotas (LP: #1849483)
- SAUCE: shiftfs: drop CAP_SYS_RESOURCE from effective capabilities

  * shiftfs: fix fallocate() (LP: #1849482)
- SAUCE: shiftfs: setup correct s_maxbytes limit

  * Bluetooth: hidp: Fix assumptions on the return value of hidp_send_message
(LP: #1850443)
- Bluetooth: hidp: Fix assumptions on the return value of hidp_send_message

  * [SRU][B/OEM-B/OEM-OSP1/D/E] UBUNTU: SAUCE: add rtl623 codec support and fix
mic issues (LP: #1850599)
- SAUCE: ALSA: hda/realtek - Add support for ALC623
- SAUCE: ALSA: hda/realtek - Fix 2 front mics of codec 0x623

  * NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between
client and server (LP: #1828978)
- NFSv4.1: Avoid false retries when RPC calls are interrupted

  * SUNRPC: Use after free when GSSD credentials are invalid causes oops
(LP: #1842037)
- SUNRPC: Clean up
- SUNRPC: Fix a use after free when a server rejects the RPCSEC_GSS 
credential

  * Suppress "hid_field_extract() called with n (192) > 32!" message floods
(LP: #1850600)
- 

[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-11-20 Thread Christian Brauner
** Tags removed: verification-needed-disco verification-needed-eoan
** Tags added: verification-done-disco verification-done-eoan

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-11-14 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the 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-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag 'verification-needed-disco' to 'verification-failed-disco'.

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: verification-needed-disco

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-11-14 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the 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-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

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: verification-needed-eoan

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-11-13 Thread Stefan Bader
** Changed in: linux (Ubuntu Disco)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-11-12 Thread Khaled El Mously
** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-11-08 Thread Manoj Iyer
** Changed in: linux (Ubuntu Disco)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-11-06 Thread Manoj Iyer
** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => In Progress

** Changed in: ubuntu-kernel-tests
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Eoan)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  In Progress

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-10-29 Thread Khaled El Mously
** Changed in: linux (Ubuntu Disco)
   Status: Fix Committed => Confirmed

** Changed in: linux (Ubuntu Eoan)
   Status: Fix Committed => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-10-28 Thread Khaled El Mously
** Changed in: linux (Ubuntu Disco)
   Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-10-28 Thread Po-Hsu Lin
** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: 5.3 bionic sru-20190930 ubuntu-kernel-selftests

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-10-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu Eoan)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-10-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu Disco)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-10-22 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  New
Status in linux source package in Eoan:
  New

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

2019-10-22 Thread Po-Hsu Lin
** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849281

Title:
  seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  New
Status in linux source package in Eoan:
  New

Bug description:
  SRU Justification

  Impact:
  We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that 
supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not 
SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The 
reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under 
the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER.

  Fix:
  The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
  ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
  work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
  support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of
  the former ifndef's scope.

  Regression Potential:
  Limited to seccomp selftests.

  Test Case:
  Compile the selftests on a kernel that supports 
SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support 
SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds.

  Target Kernels: All current LTS kernels with access to a 5.0 kernel.

  Patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp