From: "Lukáš Czerner" <lczerner@redhat.com>
To: Taesoo Kim <tsgatesv@gmail.com>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, taesoo@gatech.edu,
changwoo@gatech.edu, sanidhya@gatech.edu, blee@gatech.edu,
csong84@gatech.edu
Subject: Re: [PATCH 1/1] jbd2: fix incorrect unlock on j_list_lock
Date: Wed, 18 Mar 2015 11:43:21 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1503181142160.23465@localhost.localdomain> (raw)
In-Reply-To: <1426644518-29680-1-git-send-email-tsgatesv@gmail.com>
On Tue, 17 Mar 2015, Taesoo Kim wrote:
> Date: Tue, 17 Mar 2015 22:08:38 -0400
> From: Taesoo Kim <tsgatesv@gmail.com>
> To: tytso@mit.edu, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
> Cc: taesoo@gatech.edu, changwoo@gatech.edu, sanidhya@gatech.edu,
> blee@gatech.edu, csong84@gatech.edu, Taesoo Kim <tsgatesv@gmail.com>
> Subject: [PATCH 1/1] jbd2: fix incorrect unlock on j_list_lock
>
> When 'jh->b_transaction == transaction' (asserted by below)
>
> J_ASSERT_JH(jh, (jh->b_transaction == transaction || ...
>
> 'journal->j_list_lock' will be incorrectly unlocked, since
> the the lock is aquired only at the end of if / else-if
> statements (missing the else case).
The patch looks good, thanks.
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
Btw, were you able to reproduce the problem, or have you seen the
problem in the wild ? Or did you just spot it in the code ?
Thanks!
-Lukas
>
> Signed-off-by: Taesoo Kim <tsgatesv@gmail.com>
> ---
> fs/jbd2/transaction.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/jbd2/transaction.c b/fs/jbd2/transaction.c
> index 5f09370..edb7f59 100644
> --- a/fs/jbd2/transaction.c
> +++ b/fs/jbd2/transaction.c
> @@ -1091,6 +1091,7 @@ int jbd2_journal_get_create_access(handle_t *handle, struct buffer_head *bh)
> JBUFFER_TRACE(jh, "file as BJ_Reserved");
> spin_lock(&journal->j_list_lock);
> __jbd2_journal_file_buffer(jh, transaction, BJ_Reserved);
> + spin_unlock(&journal->j_list_lock);
> } else if (jh->b_transaction == journal->j_committing_transaction) {
> /* first access by this transaction */
> jh->b_modified = 0;
> @@ -1098,8 +1099,8 @@ int jbd2_journal_get_create_access(handle_t *handle, struct buffer_head *bh)
> JBUFFER_TRACE(jh, "set next transaction");
> spin_lock(&journal->j_list_lock);
> jh->b_next_transaction = transaction;
> + spin_unlock(&journal->j_list_lock);
> }
> - spin_unlock(&journal->j_list_lock);
> jbd_unlock_bh_state(bh);
>
> /*
> --
> 2.3.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-03-18 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 2:08 [PATCH 1/1] jbd2: fix incorrect unlock on j_list_lock Taesoo Kim
2015-03-18 10:43 ` Lukáš Czerner [this message]
2015-03-18 17:39 ` Taesoo Kim
2015-03-19 9:48 ` Lukáš Czerner
2015-03-19 12:02 ` Taesoo Kim
2015-03-19 12:13 ` Lukáš Czerner
2016-10-12 22:58 ` Andreas Dilger
2016-10-13 3:21 ` Theodore Ts'o
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=alpine.LFD.2.00.1503181142160.23465@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=blee@gatech.edu \
--cc=changwoo@gatech.edu \
--cc=csong84@gatech.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanidhya@gatech.edu \
--cc=taesoo@gatech.edu \
--cc=tsgatesv@gmail.com \
--cc=tytso@mit.edu \
/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