From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261634AbVCWPbV (ORCPT ); Wed, 23 Mar 2005 10:31:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261633AbVCWPaF (ORCPT ); Wed, 23 Mar 2005 10:30:05 -0500 Received: from e31.co.us.ibm.com ([32.97.110.129]:26071 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id S262686AbVCWP3T (ORCPT ); Wed, 23 Mar 2005 10:29:19 -0500 From: Tom Zanussi MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16961.35656.576684.890542@tut.ibm.com> Date: Wed, 23 Mar 2005 09:29:12 -0600 To: kingsley@aurema.com Cc: Tom Zanussi , Karim Yaghmour , linux-kernel@vger.kernel.org Subject: Re: read() on relayfs channel returns premature 0 In-Reply-To: <20050323090254.GA10630@aurema.com> References: <20050323090254.GA10630@aurema.com> X-Mailer: VM 7.17 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org kingsley@aurema.com writes: > > Now I understand that this is not the latest release of relayfs (there > are the redux patches, which I have yet to try). Nonetheless I'd like > to know whether this behaviour is deliberate. Is it? Nope, looks like you've found a bug - thanks for the patch. Any chance you can send me your module so I can easily reproduce the problem and test the fix? Thanks, Tom