All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taesoo Kim <taesoo@gatech.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Taesoo Kim <tsgatesv@gmail.com>,
	tytso@mit.edu, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org, 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: Thu, 19 Mar 2015 08:02:43 -0400	[thread overview]
Message-ID: <20150319120243.GG31460@taesoo.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1503191046280.29774@localhost.localdomain>

On 03/19/15 at 10:48am, Lukáš Czerner wrote:
> On Wed, 18 Mar 2015, Taesoo Kim wrote:
> 
> > Date: Wed, 18 Mar 2015 13:39:31 -0400
> > From: Taesoo Kim <taesoo@gatech.edu>
> > To: Lukáš Czerner <lczerner@redhat.com>
> > Cc: Taesoo Kim <tsgatesv@gmail.com>, tytso@mit.edu,
> >     linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
> >     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
> > 
> > > The patch looks good, thanks.
> > 
> > Thank you.
> >  
> > > 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 ?
> > 
> > We are developing a static checker to spot inconsistent programming
> > patterns; our first goal is to scan over existing filesystems and
> > figure out how they are implemented differently (or similarly). We
> > will report bugs in sequence as soon as our team confirm (just start
> > sending patches to other fs).
> 
> And this was found but it ?

Our current prototype.
 
> But anyway it sounds really interesting, do you have any more
> information you can share about the project ? Project website,
> description, or source code would be great :)

We need 1-2 months to wrap up. I would say, right after the deadline,
we plan to make the code/result publicly available :)

Taesoo
 
> Thanks!
> -Lukas
> 
> > 
> > Thanks,
> > Taesoo
> > 
> > > 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
> > > > 
> > 

--
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

WARNING: multiple messages have this Message-ID (diff)
From: Taesoo Kim <taesoo@gatech.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Taesoo Kim <tsgatesv@gmail.com>,
	tytso@mit.edu, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org, 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: Thu, 19 Mar 2015 08:02:43 -0400	[thread overview]
Message-ID: <20150319120243.GG31460@taesoo.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1503191046280.29774@localhost.localdomain>

On 03/19/15 at 10:48am, Lukáš Czerner wrote:
> On Wed, 18 Mar 2015, Taesoo Kim wrote:
> 
> > Date: Wed, 18 Mar 2015 13:39:31 -0400
> > From: Taesoo Kim <taesoo@gatech.edu>
> > To: Lukáš Czerner <lczerner@redhat.com>
> > Cc: Taesoo Kim <tsgatesv@gmail.com>, tytso@mit.edu,
> >     linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
> >     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
> > 
> > > The patch looks good, thanks.
> > 
> > Thank you.
> >  
> > > 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 ?
> > 
> > We are developing a static checker to spot inconsistent programming
> > patterns; our first goal is to scan over existing filesystems and
> > figure out how they are implemented differently (or similarly). We
> > will report bugs in sequence as soon as our team confirm (just start
> > sending patches to other fs).
> 
> And this was found but it ?

Our current prototype.
 
> But anyway it sounds really interesting, do you have any more
> information you can share about the project ? Project website,
> description, or source code would be great :)

We need 1-2 months to wrap up. I would say, right after the deadline,
we plan to make the code/result publicly available :)

Taesoo
 
> Thanks!
> -Lukas
> 
> > 
> > Thanks,
> > Taesoo
> > 
> > > 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
> > > > 
> > 


  reply	other threads:[~2015-03-19 12:02 UTC|newest]

Thread overview: 9+ 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
2015-03-18 17:39   ` Taesoo Kim
2015-03-19  9:48     ` Lukáš Czerner
2015-03-19 12:02       ` Taesoo Kim [this message]
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=20150319120243.GG31460@taesoo.org \
    --to=taesoo@gatech.edu \
    --cc=blee@gatech.edu \
    --cc=changwoo@gatech.edu \
    --cc=csong84@gatech.edu \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sanidhya@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.