From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932828AbcLHG6h (ORCPT ); Thu, 8 Dec 2016 01:58:37 -0500 Received: from mail-wm0-f66.google.com ([74.125.82.66]:36265 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932776AbcLHG6f (ORCPT ); Thu, 8 Dec 2016 01:58:35 -0500 Subject: Re: [PATCH v2] inotify: Convert to using per-namespace limits To: "Eric W. Biederman" , Nikolay Borisov References: <20161010164046.GG24081@quack2.suse.cz> <1476171382-11911-1-git-send-email-kernel@kyup.com> <674564a4-ff05-b4d6-4a98-8cfc2e609325@kyup.com> <87twafci52.fsf@xmission.com> Cc: containers@lists.linux-foundation.org, jack@suse.cz, linux-kernel@vger.kernel.org, serge@hallyn.com From: Nikolay Borisov Message-ID: Date: Thu, 8 Dec 2016 08:58:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <87twafci52.fsf@xmission.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8.12.2016 03:40, Eric W. Biederman wrote: > Nikolay Borisov 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 >