summaryrefslogtreecommitdiff
path: root/bpf_jit_disasm.c
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2015-07-30 14:54:31 +0200
committerTobias Klauser <tklauser@distanz.ch>2015-07-30 14:54:31 +0200
commitd19a87a0b2d6c8a282a04ef80bee5a3b9f4547a1 (patch)
treeedefb0359c8eaf1792438aefd05dff2e202bb1ee /bpf_jit_disasm.c
parent9b0949b728eae42550e5adc6ff67063499d53044 (diff)
sock: Avoid setting negative socket memory values
When getting of the initial values fails in set_system_socket_memory(), we store -1 for the values. Avoid writing these back (and causing an error message) when calling reset_system_socket_memory(). Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'bpf_jit_disasm.c')
0 files changed, 0 insertions, 0 deletions
is can result in a situation where after a log replay we end up with an extent not marked anymore as prealloc but it was only partially written (or not written at all), exposing random, stale or garbage data corresponding to the unwritten pages and without any checksums in the csum tree covering the extent's range. This is an extension of what was done in commit de0ee0edb21f ("Btrfs: fix race between fsync and lockless direct IO writes"). So fix this by creating first the ordered extent and then the extent map, so that this way if the fast fsync patch collects the new extent map it also collects the corresponding ordered extent. Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: Josef Bacik <jbacik@fb.com>
Diffstat