From: Nikolay Borisov <n.borisov.lkml@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
Nikolay Borisov <kernel@kyup.com>
Cc: containers@lists.linux-foundation.org, jack@suse.cz,
linux-kernel@vger.kernel.org, serge@hallyn.com
Subject: Re: [PATCH v2] inotify: Convert to using per-namespace limits
Date: Thu, 8 Dec 2016 08:58:31 +0200 [thread overview]
Message-ID: <e86b3a4f-51d5-ea61-93f3-883fe2dbcf34@gmail.com> (raw)
In-Reply-To: <87twafci52.fsf@xmission.com>
On 8.12.2016 03:40, Eric W. Biederman wrote:
> Nikolay Borisov <kernel@kyup.com> writes:
>
>> Gentle ping, now that rc1 has shipped and Jan's sysctl concern hopefully
>> resolved.
>
> After getting slowed down by some fixes I am now taking a hard look at
> your patch in the hopes of merging it.
>
> Did you happen to see the kbuild test roboot boot failures and did you
> happen to look into what caused them? I have just skimmed them and it
> appears to be related to your patch.
I saw them in the beginning but they did look like a generic memory
corruption and I believe at the time those patches were submitted there
was a lingering memory corruption hitting various patches. Thus I didn't
think it was related to my patches. I've since left my work so been
taking a bit of time off and haven't looked really hard, so those
patches have been kind of lingering.
But now that you mention it I will try and take a second look to see
what might cause the memory corruption? Is there a way to force 0day to
re-run them to see whether the failure was indeed caused by my patches
or were intermittent?
Regards,
Nikolay
>
> Eric
>
> _______________________________________________
> Containers mailing list
> Containers@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/containers
>
next prev parent reply other threads:[~2016-12-08 6:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 10:46 [PATCH] inotify: Convert to using per-namespace limits Nikolay Borisov
2016-10-07 18:14 ` Eric W. Biederman
2016-10-10 6:44 ` Nikolay Borisov
2016-10-10 16:40 ` Jan Kara
2016-10-10 20:49 ` Eric W. Biederman
2016-10-10 21:54 ` Nikolay Borisov
2016-10-10 22:39 ` Eric W. Biederman
2016-10-11 7:36 ` [PATCH v2] " Nikolay Borisov
2016-10-14 2:31 ` [lkp] [inotify] 464e1236c3: BUG kmalloc-512 (Not tainted): Freepointer corrupt kernel test robot
2016-10-24 6:47 ` [PATCH v2] inotify: Convert to using per-namespace limits Nikolay Borisov
2016-10-27 15:46 ` Eric W. Biederman
2016-12-08 1:40 ` Eric W. Biederman
2016-12-08 6:58 ` Nikolay Borisov [this message]
2016-12-08 8:14 ` Nikolay Borisov
2016-12-09 5:38 ` Eric W. Biederman
2016-12-09 2:50 ` Eric W. Biederman
2016-10-24 7:48 ` Jan Kara
2016-11-14 6:04 ` Serge E. Hallyn
2016-10-09 5:55 ` [lkp] [inotify] 1109954e99: BUG kmalloc-512 (Not tainted): Freepointer corrupt kernel test robot
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=e86b3a4f-51d5-ea61-93f3-883fe2dbcf34@gmail.com \
--to=n.borisov.lkml@gmail.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=jack@suse.cz \
--cc=kernel@kyup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serge@hallyn.com \
/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).