Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The v4.13.3 upstream stable
patch set is now available. It should be included in the Ubuntu
kernel as well.
git://git.kernel.org/
TEST CASE: TBD
The following patches from the v4.13.3 stable release shall be
applied:
Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
Revert "net: fix percpu memory leaks"
gianfar: Fix Tx flow control deactivation
vhost_net: correctly check tx avail during rx busy polling
ip6_gre: update mtu properly in ip6gre_err
udp: drop head states only when all skb references are gone
ipv6: fix memory leak with multiple tables during netns destruction
ipv6: fix typo in fib6_net_exit()
sctp: fix missing wake ups in some situations
tcp: fix a request socket leak
ip_tunnel: fix setting ttl and tos value in collect_md mode
f2fs: let fill_super handle roll-forward errors
f2fs: check hot_data for roll-forward recovery
thunderbolt: Remove superfluous check
thunderbolt: Make key root-only accessible
thunderbolt: Allow clearing the key
x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison pages
ovl: fix false positive ESTALE on lookup
fuse: allow server to run in different pid_ns
idr: remove WARN_ON_ONCE() when trying to replace negative ID
libnvdimm, btt: check memory allocation failure
libnvdimm: fix integer overflow static analysis warning
xfs: write unmount record for ro mounts
xfs: toggle readonly state around xfs_log_mount_finish
xfs: Add infrastructure needed for error propagation during buffer IO failure
xfs: Properly retry failed inode items in case of error during buffer writeback
xfs: fix recovery failure when log record header wraps log end
xfs: always verify the log tail during recovery
xfs: fix log recovery corruption error due to tail overwrite
xfs: handle -EFSCORRUPTED during head/tail verification
xfs: stop searching for free slots in an inode chunk when there are none
xfs: evict all inodes involved with log redo item
xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
xfs: open-code xfs_buf_item_dirty()
xfs: remove unnecessary dirty bli format check for ordered bufs
xfs: ordered buffer log items are never formatted
xfs: refactor buffer logging into buffer dirtying helper
xfs: don't log dirty ranges for ordered buffers
xfs: skip bmbt block ino validation during owner change
xfs: move bmbt owner change to last step of extent swap
xfs: disallow marking previously dirty buffers as ordered
xfs: relog dirty buffers during swapext bmbt owner change
xfs: disable per-inode DAX flag
xfs: fix incorrect log_flushed on fsync
xfs: don't set v3 xflags for v2 inodes
xfs: open code end_buffer_async_write in xfs_finish_page_writeback
xfs: use kmem_free to free return value of kmem_zalloc
md/raid1/10: reset bio allocated from mempool
md/raid5: release/flush io in raid5_do_work()
xfs: fix compiler warnings
Linux 4.13.3
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Tags: kernel-stable-tracking-bug
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The v4.13.3 upstream stable
+ patch set is now available. It should be included in the Ubuntu
+ kernel as well.
- Impact:
- The upstream process for stable tree updates is quite similar
- in scope to the Ubuntu SRU process, e.g., each patch has to
- demonstrably fix a bug, and each patch is vetted by upstream
- by originating either directly from a mainline/stable Linux tree or
- a minimally backported form of that patch. The v4.13.3 upstream stable
- patch set is now available. It should be included in the Ubuntu
- kernel as well.
+ git://git.kernel.org/
- git://git.kernel.org/
+ TEST CASE: TBD
- TEST CASE: TBD
+ The following patches from the v4.13.3 stable release shall be
+ applied:
- The following patches from the v4.13.3 stable release shall be
- applied:
+ Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
+ Revert "net: fix percpu memory leaks"
+ gianfar: Fix Tx flow control deactivation
+ vhost_net: correctly check tx avail during rx busy polling
+ ip6_gre: update mtu properly in ip6gre_err
+ udp: drop head states only when all skb references are gone
+ ipv6: fix memory leak with multiple tables during netns destruction
+ ipv6: fix typo in fib6_net_exit()
+ sctp: fix missing wake ups in some situations
+ tcp: fix a request socket leak
+ ip_tunnel: fix setting ttl and tos value in collect_md mode
+ f2fs: let fill_super handle roll-forward errors
+ f2fs: check hot_data for roll-forward recovery
+ thunderbolt: Remove superfluous check
+ thunderbolt: Make key root-only accessible
+ thunderbolt: Allow clearing the key
+ x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
+ x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
+ x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
+ x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison pages
+ ovl: fix false positive ESTALE on lookup
+ fuse: allow server to run in different pid_ns
+ idr: remove WARN_ON_ONCE() when trying to replace negative ID
+ libnvdimm, btt: check memory allocation failure
+ libnvdimm: fix integer overflow static analysis warning
+ xfs: write unmount record for ro mounts
+ xfs: toggle readonly state around xfs_log_mount_finish
+ xfs: Add infrastructure needed for error propagation during buffer IO failure
+ xfs: Properly retry failed inode items in case of error during buffer
writeback
+ xfs: fix recovery failure when log record header wraps log end
+ xfs: always verify the log tail during recovery
+ xfs: fix log recovery corruption error due to tail overwrite
+ xfs: handle -EFSCORRUPTED during head/tail verification
+ xfs: stop searching for free slots in an inode chunk when there are none
+ xfs: evict all inodes involved with log redo item
+ xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
+ xfs: open-code xfs_buf_item_dirty()
+ xfs: remove unnecessary dirty bli format check for ordered bufs
+ xfs: ordered buffer log items are never formatted
+ xfs: refactor buffer logging into buffer dirtying helper
+ xfs: don't log dirty ranges for ordered buffers
+ xfs: skip bmbt block ino validation during owner change
+ xfs: move bmbt owner change to last step of extent swap
+ xfs: disallow marking previously dirty buffers as ordered
+ xfs: relog dirty buffers during swapext bmbt owner change
+ xfs: disable per-inode DAX flag
+ xfs: fix incorrect log_flushed on fsync
+ xfs: don't set v3 xflags for v2 inodes
+ xfs: open code end_buffer_async_write in xfs_finish_page_writeback
+ xfs: use kmem_free to free return value of kmem_zalloc
+ md/raid1/10: reset bio allocated from mempool
+ md/raid5: release/flush io in raid5_do_work()
+ xfs: fix compiler warnings
+ Linux 4.13.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718412
Title:
Artful update to v4.13.3 stable release
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718412/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
