Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263741AbUFFPY7 (ORCPT ); Sun, 6 Jun 2004 11:24:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263743AbUFFPY7 (ORCPT ); Sun, 6 Jun 2004 11:24:59 -0400 Received: from [198.95.226.53] ([198.95.226.53]:63931 "EHLO mx01.netapp.com") by vger.kernel.org with ESMTP id S263001AbUFFPY5 convert rfc822-to-8bit (ORCPT ); Sun, 6 Jun 2004 11:24:57 -0400 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Subject: RE: Killing POSIX deadlock detection Date: Sun, 6 Jun 2004 08:24:24 -0700 Message-ID: <482A3FA0050D21419C269D13989C61130435E200@lavender-fe.eng.netapp.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Killing POSIX deadlock detection Thread-Index: AcRLyht/oWKQZLK+Q5OCX1MHH3QKhQAD8IWw From: "Lever, Charles" To: "Matthew Wilcox" , "Stephen Rothwell" Cc: , , , Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 638 Lines: 15 > So, final call. Any objections to never returning -EDEADLCK? not an objection, but a consideration. is this a change that belongs in 2.6? it does significantly change the behavior of the system call API, and could "break" applications. unless this fixes a significant bug, perhaps it should wait for 2.7? that would give fair warning to developers who need to fix their broken programs. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/