aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-memcpy.c
diff options
context:
space:
mode:
authorLinus Torvalds <[email protected]>2023-07-28 10:15:44 -0700
committerLinus Torvalds <[email protected]>2023-07-28 10:15:44 -0700
commit0299a13af0be43f2679047c7236e3a58e587f3f8 (patch)
treef456d937ffb8ccd40ec62b0ae1a6545d9ca8a873 /lib/test_fortify/write_overflow-memcpy.c
parentc75981a1be350f14dbfca56e62bea077dafdad96 (diff)
parentb7c822fa6b7701b17e139f1c562fc24135880ed4 (diff)
Merge tag 'for-linus-iommufd' of git://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd
Pull iommufd fixes from Jason Gunthorpe: "Two user triggerable problems: - Syzkaller found a way to trigger a WARN_ON and leak memory by racing destroy with other actions - There is still a bug in the "batch carry" stuff that gets invoked for complex cases with accesses and unmapping of huge pages. The test suite found this (triggers rarely)" * tag 'for-linus-iommufd' of git://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd: iommufd: Set end correctly when doing batch carry iommufd: IOMMUFD_DESTROY should not increase the refcount
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions