All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <zanussi@us.ibm.com>
To: Kingsley Cheung <kingsley@aurema.com>
Cc: Tom Zanussi <zanussi@us.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] relayfs crash
Date: Sun, 6 Feb 2005 22:42:27 -0600	[thread overview]
Message-ID: <16902.61875.963828.513606@tut.ibm.com> (raw)
In-Reply-To: <20050207030444.GF27268@aurema.com>

Kingsley Cheung writes:
 > 
 > To solve the problem I applied a patch similar to the one you posted
 > back in July and it fixed the problem.  Could we consider putting this
 > patch into relayfs? Its similar to the one posted in July 2004, except
 > it also moves clear_readers() before INIT_WORK in relay_release (is
 > that acceptable?).
 > 

Yes, for some reason the July patch never got applied to that (now
outdated) 2.6.10 version of relayfs - either that patch or yours
should fix the problem - thanks for sending it.  In any case, the
version of relayfs you're using is now ancient history - the latest
redux versions of relayfs recently posted to lkml have completely
changed or removed all that code, so you might want to try testing
with the latest patch (which I'm still reworking parts of even now).

Thanks,

Tom



  parent reply	other threads:[~2005-02-07  4:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20  6:23 [PATCH] relayfs redux for 2.6.10: lean and mean Karim Yaghmour
2005-01-20 14:50 ` Greg KH
2005-01-21  1:38   ` Karim Yaghmour
2005-01-21  2:15     ` Peter Williams
2005-01-21  6:39       ` Greg KH
2005-01-21  7:27         ` Peter Williams
2005-01-21  7:46           ` Greg KH
2005-01-21  6:43     ` Greg KH
2005-01-23  8:07       ` Karim Yaghmour
2005-01-20 15:06 ` Greg KH
2005-01-20 19:51 ` Pekka Enberg
2005-02-07  3:04 ` [PATCH] relayfs crash Kingsley Cheung
2005-02-07  3:16   ` Karim Yaghmour
2005-02-07  4:42   ` Tom Zanussi [this message]
2005-02-07  4:47     ` Kingsley Cheung

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=16902.61875.963828.513606@tut.ibm.com \
    --to=zanussi@us.ibm.com \
    --cc=kingsley@aurema.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.