public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: viro@math.psu.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Clean up refcounting on filesystems
Date: Mon, 13 Jan 2003 01:25:20 +0100	[thread overview]
Message-ID: <3E220770.734F8553@linux-m68k.org> (raw)
In-Reply-To: 20030111110623.08E2B2C0BC@lists.samba.org

Hi,

Rusty Russell wrote:

>         This gets rid of the hacky module count reentry, by holding a
> reference count per mount, rather than per superblock.  The additional
> field to struct vfsmount is slightly gratuitous, but nice and
> explicit.  Minor collateral cleanups.

I hoped Al would answer, but so I have to ask again.
What are you trying to fix with this? AFAICT module init races are still
there, how do you want to fix them and how will this patch help?
Rusty, could I please, please, please (with sugar on top) get an answer
to any of my questions from you?

bye, Roman

      reply	other threads:[~2003-01-13  0:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-11 11:03 [PATCH] Clean up refcounting on filesystems Rusty Russell
2003-01-13  0:25 ` Roman Zippel [this message]

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=3E220770.734F8553@linux-m68k.org \
    --to=zippel@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=viro@math.psu.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox