summaryrefslogtreecommitdiff
path: root/.zsh/completion/_netsniff-ng.zsh
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2021-03-29 19:35:14 +0200
committerTobias Klauser <tklauser@distanz.ch>2021-03-29 19:35:14 +0200
commitfb509f07440b2914599ac91b514251c12585d084 (patch)
tree99d61431f6b6549562595bec7cdd7b0beb2e2d1a /.zsh/completion/_netsniff-ng.zsh
parent960e368b3832ba67722ae801d0f4ae49cdecd8a4 (diff)
zshrc: source gcloud completion config if available
Diffstat (limited to '.zsh/completion/_netsniff-ng.zsh')
0 files changed, 0 insertions, 0 deletions
y been converted to a real allocation. For COW writes where we move the extent from the COW to the data fork after I/O completion the race is, however, not quite as harmless. In the worst case we are now calling xfs_bmapi_write on a region that contains hole in the COW work, which will trip up an assert in debug builds or lead to file system corruption in non-debug builds. This seems to be reproducible with workloads of small O_DSYNC write, although so far I've not managed to come up with a with an isolated reproducer. The fix for the issue is relatively simple: tell xfs_bmapi_write that we are only asked to convert delayed allocations and skip holes in that case. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Brian Foster <bfoster@redhat.com> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Diffstat (limited to 'sound/pci')