Searched hist:"004915 a96a7a40e942ac85e6d22518cbcd283506" (Results 1 – 9 of 9) sorted by relevance
/qemu/tests/unit/ |
H A D | test-bdrv-graph-mod.c | 004915a96a7a40e942ac85e6d22518cbcd283506 Fri Oct 27 15:53:26 UTC 2023 Kevin Wolf <kwolf@redhat.com> block: Protect bs->backing with graph_lock
Almost all functions that access bs->backing already take the graph lock now. Add locking to the remaining users and finally annotate the struct field itself as protected by the graph lock.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20231027155333.420094-18-kwolf@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
H A D | test-bdrv-drain.c | 004915a96a7a40e942ac85e6d22518cbcd283506 Fri Oct 27 15:53:26 UTC 2023 Kevin Wolf <kwolf@redhat.com> block: Protect bs->backing with graph_lock
Almost all functions that access bs->backing already take the graph lock now. Add locking to the remaining users and finally annotate the struct field itself as protected by the graph lock.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20231027155333.420094-18-kwolf@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
/qemu/include/block/ |
H A D | block_int-common.h | 004915a96a7a40e942ac85e6d22518cbcd283506 Fri Oct 27 15:53:26 UTC 2023 Kevin Wolf <kwolf@redhat.com> block: Protect bs->backing with graph_lock
Almost all functions that access bs->backing already take the graph lock now. Add locking to the remaining users and finally annotate the struct field itself as protected by the graph lock.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20231027155333.420094-18-kwolf@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
/qemu/block/ |
H A D | replication.c | 004915a96a7a40e942ac85e6d22518cbcd283506 Fri Oct 27 15:53:26 UTC 2023 Kevin Wolf <kwolf@redhat.com> block: Protect bs->backing with graph_lock
Almost all functions that access bs->backing already take the graph lock now. Add locking to the remaining users and finally annotate the struct field itself as protected by the graph lock.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20231027155333.420094-18-kwolf@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
H A D | commit.c | 004915a96a7a40e942ac85e6d22518cbcd283506 Fri Oct 27 15:53:26 UTC 2023 Kevin Wolf <kwolf@redhat.com> block: Protect bs->backing with graph_lock
Almost all functions that access bs->backing already take the graph lock now. Add locking to the remaining users and finally annotate the struct field itself as protected by the graph lock.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20231027155333.420094-18-kwolf@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
H A D | vmdk.c | 004915a96a7a40e942ac85e6d22518cbcd283506 Fri Oct 27 15:53:26 UTC 2023 Kevin Wolf <kwolf@redhat.com> block: Protect bs->backing with graph_lock
Almost all functions that access bs->backing already take the graph lock now. Add locking to the remaining users and finally annotate the struct field itself as protected by the graph lock.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20231027155333.420094-18-kwolf@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
H A D | qed.c | 004915a96a7a40e942ac85e6d22518cbcd283506 Fri Oct 27 15:53:26 UTC 2023 Kevin Wolf <kwolf@redhat.com> block: Protect bs->backing with graph_lock
Almost all functions that access bs->backing already take the graph lock now. Add locking to the remaining users and finally annotate the struct field itself as protected by the graph lock.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20231027155333.420094-18-kwolf@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
H A D | mirror.c | 004915a96a7a40e942ac85e6d22518cbcd283506 Fri Oct 27 15:53:26 UTC 2023 Kevin Wolf <kwolf@redhat.com> block: Protect bs->backing with graph_lock
Almost all functions that access bs->backing already take the graph lock now. Add locking to the remaining users and finally annotate the struct field itself as protected by the graph lock.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20231027155333.420094-18-kwolf@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
/qemu/ |
H A D | block.c | 004915a96a7a40e942ac85e6d22518cbcd283506 Fri Oct 27 15:53:26 UTC 2023 Kevin Wolf <kwolf@redhat.com> block: Protect bs->backing with graph_lock
Almost all functions that access bs->backing already take the graph lock now. Add locking to the remaining users and finally annotate the struct field itself as protected by the graph lock.
Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20231027155333.420094-18-kwolf@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|