aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/crypto/testmgr.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2022-03-26 11:59:30 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2022-03-26 11:59:30 -0700
commit752d422e74c41084c3c9c9a159cb8d2795fa0c22 (patch)
tree61ab9a5fd11d7ad1f29d1d9c2f8e59210849fd7b /crypto/testmgr.c
parentMerge tag 'for-5.18/write-streams-2022-03-18' of git://git.kernel.dk/linux-block (diff)
parentfs: do not pass __GFP_HIGHMEM to bio_alloc in do_mpage_readpage (diff)
downloadwireguard-linux-752d422e74c41084c3c9c9a159cb8d2795fa0c22.tar.xz
wireguard-linux-752d422e74c41084c3c9c9a159cb8d2795fa0c22.zip
Merge tag 'for-5.18/alloc-cleanups-2022-03-25' of git://git.kernel.dk/linux-block
Pull bio allocation fix from Jens Axboe: "We got some reports of users seeing: Unexpected gfp: 0x2 (__GFP_HIGHMEM). Fixing up to gfp: 0x1192888 which is a regression caused by the bio allocation cleanups" * tag 'for-5.18/alloc-cleanups-2022-03-25' of git://git.kernel.dk/linux-block: fs: do not pass __GFP_HIGHMEM to bio_alloc in do_mpage_readpage
Diffstat (limited to 'crypto/testmgr.c')
0 files changed, 0 insertions, 0 deletions