Re: [PATCH v2] Updated locking documentation for transaction_t

2021-02-11 Thread Jan Kara
On Thu 11-02-21 14:54:23, Alexander Lochmann wrote: > Some members of transaction_t are allowed to be read without > any lock being held if accessed from the correct context. > We used LockDoc's findings to determine those members. > Each member of them is marked with a short comment: > "no lock

[PATCH v2] Updated locking documentation for transaction_t

2021-02-11 Thread Alexander Lochmann
Some members of transaction_t are allowed to be read without any lock being held if accessed from the correct context. We used LockDoc's findings to determine those members. Each member of them is marked with a short comment: "no lock needed for jbd2 thread". Signed-off-by: Alexander Lochmann

Re: [PATCH v2] Updated locking documentation for transaction_t

2019-03-19 Thread Jan Kara
On Mon 18-03-19 19:42:37, Alexander Lochmann wrote: > We used LockDoc to derive locking rules for each member > of struct transaction_t. > Based on those results, we extended the existing documentation > by more members of struct inode, and updated the existing > documentation. > > Signed-off-by:

[PATCH v2] Updated locking documentation for transaction_t

2019-03-18 Thread Alexander Lochmann
We used LockDoc to derive locking rules for each member of struct transaction_t. Based on those results, we extended the existing documentation by more members of struct inode, and updated the existing documentation. Signed-off-by: Alexander Lochmann Signed-off-by: Horst Schirmeier ---