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 ne
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
Sig
Thanks, Ted, for your feedback!
I'll submit a modified version.
- Alex
On 07.04.19 18:52, Theodore Ts'o wrote:
> On Mon, Mar 18, 2019 at 07:42:37PM +0100, Alexander Lochmann wrote:
>> /*t
>> - * Where in the log does this transaction's commit start? [no locking]
>> + * Where in the l
On Mon, Mar 18, 2019 at 07:42:37PM +0100, Alexander Lochmann wrote:
> /*t
> - * Where in the log does this transaction's commit start? [no locking]
> + * Where in the log does this transaction's commit start?
> + * [journal_t.j_state_lock]
>*/
> unsigned long
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:
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
---
include/
6 matches
Mail list logo
