summaryrefslogtreecommitdiff
path: root/net/mpls/Kconfig
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2023-06-15 20:19:21 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2023-06-15 20:19:21 -0700
commit0e306952d7151afdaa16e9acf280a739d1fe7b29 (patch)
treeee3cdb5f81edef216f4ab8f03e92cfa13d420963 /net/mpls/Kconfig
parent93fd8eb053800a241d09c00ef075cae0b5b03ecf (diff)
parentbe04c14a1bd262a49e5764e5cf864259b7e740fd (diff)
Merge tag 'for-6.4/dm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
Pull device mapper fixes from Mike Snitzer: - Fix DM thinp discard performance regression introduced during this merge window where DM core was splitting large discards every 128K (max_sectors_kb) rather than every 64M (discard_max_bytes). - Extend DM core LOCKFS fix, made during 6.4 merge, to also fix race between do_mount and dm's do_suspend (in addition to the earlier fix's do_mount race with dm's do_resume). - Fix DM thin metadata operations to first check if the thin-pool is in "fail_io" mode; otherwise UAF can occur. - Fix DM thinp's call to __blkdev_issue_discard to use GFP_NOIO rather than GFP_NOWAIT (__blkdev_issue_discard cannot handle NULL return from bio_alloc). * tag 'for-6.4/dm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm: dm: use op specific max_sectors when splitting abnormal io dm thin: fix issue_discard to pass GFP_NOIO to __blkdev_issue_discard dm thin metadata: check fail_io before using data_sm dm: don't lock fs when the map is NULL during suspend or resume
Diffstat (limited to 'net/mpls/Kconfig')
0 files changed, 0 insertions, 0 deletions