summaryrefslogtreecommitdiffstats
path: root/COPYING
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2020-11-08 10:11:31 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2020-11-08 10:11:31 -0800
commit6b2c4d52fd38e676fc9ab5d9241a056de565eb1a (patch)
tree78394266fc3163750fdedf14c4c6a50917c301d1 /COPYING
parent40be821d627c61ee5beb51d265af372ab29804e4 (diff)
parentb24c30c678630e48cf8e3caefe463e1c6144d029 (diff)
downloadlinux-stable-6b2c4d52fd38e676fc9ab5d9241a056de565eb1a.tar.gz
linux-stable-6b2c4d52fd38e676fc9ab5d9241a056de565eb1a.tar.bz2
linux-stable-6b2c4d52fd38e676fc9ab5d9241a056de565eb1a.zip
Merge branch 'hch' (patches from Christoph)
Merge procfs splice read fixes from Christoph Hellwig: "Greg reported a problem due to the fact that Android tests use procfs files to test splice, which stopped working with the changes for set_fs() removal. This series adds read_iter support for seq_file, and uses those for various proc files using seq_file to restore splice read support" [ Side note: Christoph initially had a scripted "move everything over" patch, which looks fine, but I personally would prefer us to actively discourage splice() on random files. So this does just the minimal basic core set of proc file op conversions. For completeness, and in case people care, that script was sed -i -e 's/\.proc_read\(\s*=\s*\)seq_read/\.proc_read_iter\1seq_read_iter/g' but I'll wait and see if somebody has a strong argument for using splice on random small /proc files before I'd run it on the whole kernel. - Linus ] * emailed patches from Christoph Hellwig <hch@lst.de>: proc "seq files": switch to ->read_iter proc "single files": switch to ->read_iter proc/stat: switch to ->read_iter proc/cpuinfo: switch to ->read_iter proc: wire up generic_file_splice_read for iter ops seq_file: add seq_read_iter
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions