On 2020/5/5 0:15, Markus Elfring wrote:
Thus, a data race can occur for tblk->flag.
To fix this data race, the spinlock log->gclock is used in
txBegin().
This data race is found by our concurrency fuzzer.
How do you think about a wording variant like the following?
Change description:
> Thus, a data race can occur for tblk->flag.
>
> To fix this data race, the spinlock log->gclock is used in
> txBegin().
>
> This data race is found by our concurrency fuzzer.
How do you think about a wording variant like the following?
Change description:
A data race can occur for the
The functions txBegin() and txLazyCommit() can be concurrently executed
in the following call contexts:
Thread1:
jfs_write_inode()
jfs_commit_inode()
txBegin()
Thread2:
jfs_lazycommit()
txLazyCommit()
In txBegin():
tblk->next = tblk->last = tblk->xflag = tblk->flag =
3 matches
Mail list logo
