From: "Theodore Ts'o" <tytso@mit.edu>
To: Alexander Lochmann <alexander.lochmann@tu-dortmund.de>
Cc: Jan Kara <jack@suse.cz>,
Horst Schirmeier <horst.schirmeier@tu-dortmund.de>,
Jan Kara <jack@suse.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Updated locking documentation for journal_t
Date: Fri, 2 Apr 2021 11:40:19 -0400 [thread overview]
Message-ID: <YGc642aVrbAN77rT@mit.edu> (raw)
In-Reply-To: <ad82c7a9-a624-4ed5-5ada-a6410c44c0b3@tu-dortmund.de>
On Thu, Feb 11, 2021 at 10:51:55AM +0100, Alexander Lochmann wrote:
> Some members of transaction_t are allowed to be read without
> any lock being held if consistency doesn't matter.
> Based on LockDoc's findings, we extended the locking
> documentation of those members.
> Each one of them is marked with a short comment:
> "no lock for quick racy checks".
>
> Signed-off-by: Alexander Lochmann <alexander.lochmann@tu-dortmund.de>
> Signed-off-by: Horst Schirmeier <horst.schirmeier@tu-dortmund.de>
> Reviewed-by: Jan Kara <jack@suse.cz>
Thanks, applied. I had to fix up the patch, which was mailer-damaged,
and I also reflowed the comments.
- Ted
prev parent reply other threads:[~2021-04-02 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 9:57 [PATCH 2/2] Updated locking documentation for journal_t Alexander Lochmann
2021-02-10 9:57 ` [PATCH 1/2] Updated locking documentation for transaction_t Alexander Lochmann
2021-02-11 9:30 ` Jan Kara
2021-02-11 9:53 ` Alexander Lochmann
2021-02-11 13:13 ` Jan Kara
2021-03-26 8:18 ` Alexander Lochmann
2021-03-29 10:14 ` Jan Kara
2021-02-11 9:37 ` [PATCH 2/2] Updated locking documentation for journal_t Jan Kara
2021-02-11 9:51 ` [PATCH v2] " Alexander Lochmann
2021-03-17 20:57 ` Alexander Lochmann
2021-04-02 15:40 ` Theodore Ts'o [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YGc642aVrbAN77rT@mit.edu \
--to=tytso@mit.edu \
--cc=alexander.lochmann@tu-dortmund.de \
--cc=horst.schirmeier@tu-dortmund.de \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).