[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1503191313120.1399@localhost.localdomain>
Date: Thu, 19 Mar 2015 13:13:39 +0100 (CET)
From: Lukáš Czerner <lczerner@...hat.com>
To: Taesoo Kim <taesoo@...ech.edu>
cc: Taesoo Kim <tsgatesv@...il.com>, tytso@....edu,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
changwoo@...ech.edu, sanidhya@...ech.edu, blee@...ech.edu,
csong84@...ech.edu
Subject: Re: [PATCH 1/1] jbd2: fix incorrect unlock on j_list_lock
On Thu, 19 Mar 2015, Taesoo Kim wrote:
> Date: Thu, 19 Mar 2015 08:02:43 -0400
> From: Taesoo Kim <taesoo@...ech.edu>
> To: Lukáš Czerner <lczerner@...hat.com>
> Cc: Taesoo Kim <tsgatesv@...il.com>, tytso@....edu,
> linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
> changwoo@...ech.edu, sanidhya@...ech.edu, blee@...ech.edu,
> csong84@...ech.edu
> Subject: Re: [PATCH 1/1] jbd2: fix incorrect unlock on j_list_lock
>
> 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@...ech.edu>
> > > To: Lukáš Czerner <lczerner@...hat.com>
> > > Cc: Taesoo Kim <tsgatesv@...il.com>, tytso@....edu,
> > > linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
> > > changwoo@...ech.edu, sanidhya@...ech.edu, blee@...ech.edu,
> > > csong84@...ech.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@...hat.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 :)
Great! Looking forward to it.
Thanks!
-Lukas
Powered by blists - more mailing lists