From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933599AbbCPSYZ (ORCPT ); Mon, 16 Mar 2015 14:24:25 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:36657 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932271AbbCPSYY (ORCPT ); Mon, 16 Mar 2015 14:24:24 -0400 Date: Mon, 16 Mar 2015 18:24:20 +0000 From: Andy Whitcroft To: Peter Hurley Cc: Greg Kroah-Hartman , Jiri Slaby , linux-kernel@vger.kernel.org, Alan Cox Subject: Re: [PATCH 1/1] pty, n_tty: continue processing input until the tty_buffer chain is flushed Message-ID: <20150316182420.GC3753@dm> References: <1426516232-25301-1-git-send-email-apw@canonical.com> <55071AEB.3030702@hurleysoftware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55071AEB.3030702@hurleysoftware.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 16, 2015 at 02:03:23PM -0400, Peter Hurley wrote: > I just managed to reproduce this problem with a test jig; > can you confirm that your self-tests also use >= 4096-byte read buffer > (which I think is necessary to trigger the worker race)? The read which triggers the EIO is indeed using a 4096 byte buffer: 1396 read(17, 0x7f78214c3b30, 4096) = -1 EIO (Input/output error) We found a simpler reproduce by than the upstart selftest which is included in the bug linked in the commit text. Specifically in comment 13 [1]. Thanks for looking at this. -apw [1] https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/comments/13