On Tue 31-10-17 13:02:21, Amir Goldstein wrote:
> On Tue, Oct 31, 2017 at 11:54 AM, Jan Kara wrote:
> > On Mon 30-10-17 21:18:09, Miklos Szeredi wrote:
> >> On Mon, Oct 30, 2017 at 6:27 PM, Jan Kara wrote:
> >> > On Fri 27-10-17 13:53:20, Jan Kara wrote:
> >> >> On
On Tue 31-10-17 13:02:21, Amir Goldstein wrote:
> On Tue, Oct 31, 2017 at 11:54 AM, Jan Kara wrote:
> > On Mon 30-10-17 21:18:09, Miklos Szeredi wrote:
> >> On Mon, Oct 30, 2017 at 6:27 PM, Jan Kara wrote:
> >> > On Fri 27-10-17 13:53:20, Jan Kara wrote:
> >> >> On Wed 25-10-17 16:31:39, Miklos
On Tue, Oct 31, 2017 at 11:54 AM, Jan Kara wrote:
> On Mon 30-10-17 21:18:09, Miklos Szeredi wrote:
>> On Mon, Oct 30, 2017 at 6:27 PM, Jan Kara wrote:
>> > On Fri 27-10-17 13:53:20, Jan Kara wrote:
>> >> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
>> >> > On Wed,
On Tue, Oct 31, 2017 at 11:54 AM, Jan Kara wrote:
> On Mon 30-10-17 21:18:09, Miklos Szeredi wrote:
>> On Mon, Oct 30, 2017 at 6:27 PM, Jan Kara wrote:
>> > On Fri 27-10-17 13:53:20, Jan Kara wrote:
>> >> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
>> >> > On Wed, Oct 25, 2017 at 10:41 AM,
On Mon 30-10-17 21:18:09, Miklos Szeredi wrote:
> On Mon, Oct 30, 2017 at 6:27 PM, Jan Kara wrote:
> > On Fri 27-10-17 13:53:20, Jan Kara wrote:
> >> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
> >> > On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi
> >> >
On Mon 30-10-17 21:18:09, Miklos Szeredi wrote:
> On Mon, Oct 30, 2017 at 6:27 PM, Jan Kara wrote:
> > On Fri 27-10-17 13:53:20, Jan Kara wrote:
> >> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
> >> > On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi
> >> > wrote:
> >> > > We discovered some
On Mon, Oct 30, 2017 at 6:27 PM, Jan Kara wrote:
> On Fri 27-10-17 13:53:20, Jan Kara wrote:
>> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
>> > On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi
>> > wrote:
>> > > We discovered some problems in the latest
On Mon, Oct 30, 2017 at 6:27 PM, Jan Kara wrote:
> On Fri 27-10-17 13:53:20, Jan Kara wrote:
>> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
>> > On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi
>> > wrote:
>> > > We discovered some problems in the latest fsnotify/fanotify codebase with
>> >
On Fri 27-10-17 13:53:20, Jan Kara wrote:
> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
> > On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi
> > wrote:
> > > We discovered some problems in the latest fsnotify/fanotify codebase with
> > > the help of a stress test (Xiong
On Fri 27-10-17 13:53:20, Jan Kara wrote:
> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
> > On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi
> > wrote:
> > > We discovered some problems in the latest fsnotify/fanotify codebase with
> > > the help of a stress test (Xiong Zhou is working on
On Fri, Oct 27, 2017 at 1:53 PM, Jan Kara wrote:
> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
>> On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi wrote:
>> > We discovered some problems in the latest fsnotify/fanotify codebase with
>> > the help of a
On Fri, Oct 27, 2017 at 1:53 PM, Jan Kara wrote:
> On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
>> On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi wrote:
>> > We discovered some problems in the latest fsnotify/fanotify codebase with
>> > the help of a stress test (Xiong Zhou is working on
On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
> On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi wrote:
> > We discovered some problems in the latest fsnotify/fanotify codebase with
> > the help of a stress test (Xiong Zhou is working on upstreaming it to
> > fstests).
> >
On Wed 25-10-17 16:31:39, Miklos Szeredi wrote:
> On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi wrote:
> > We discovered some problems in the latest fsnotify/fanotify codebase with
> > the help of a stress test (Xiong Zhou is working on upstreaming it to
> > fstests).
> >
> > This series
On Wed, Oct 25, 2017 at 5:31 PM, Miklos Szeredi wrote:
> On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi wrote:
>> We discovered some problems in the latest fsnotify/fanotify codebase with
>> the help of a stress test (Xiong Zhou is working on
On Wed, Oct 25, 2017 at 5:31 PM, Miklos Szeredi wrote:
> On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi wrote:
>> We discovered some problems in the latest fsnotify/fanotify codebase with
>> the help of a stress test (Xiong Zhou is working on upstreaming it to
>> fstests).
>>
>> This series
On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi wrote:
> We discovered some problems in the latest fsnotify/fanotify codebase with
> the help of a stress test (Xiong Zhou is working on upstreaming it to
> fstests).
>
> This series attempts to fix these. With the patch
On Wed, Oct 25, 2017 at 10:41 AM, Miklos Szeredi wrote:
> We discovered some problems in the latest fsnotify/fanotify codebase with
> the help of a stress test (Xiong Zhou is working on upstreaming it to
> fstests).
>
> This series attempts to fix these. With the patch applied the stress test
>
We discovered some problems in the latest fsnotify/fanotify codebase with
the help of a stress test (Xiong Zhou is working on upstreaming it to
fstests).
This series attempts to fix these. With the patch applied the stress test
passes.
Please review/test.
Changes in v2 (only cosmetic fixes, no
We discovered some problems in the latest fsnotify/fanotify codebase with
the help of a stress test (Xiong Zhou is working on upstreaming it to
fstests).
This series attempts to fix these. With the patch applied the stress test
passes.
Please review/test.
Changes in v2 (only cosmetic fixes, no
20 matches
Mail list logo