archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <>
To: John Zielinski <>
Subject: Re: Rootfs mounted from user space - problem with umount
Date: Sat, 29 Nov 2003 01:44:35 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

William Lee Irwin III wrote:
>> Looks like either namespace->sem or sb->s_umount; you should be able
>> to put some instrumentation code in down_write() and/or down_read() to
>> see who acquired it first by checking to see if the sem acquired belongs
>> to rootfs' sb or some namespace (doubtful you'll create many of them).

On Sat, Nov 29, 2003 at 04:40:51AM -0500, John Zielinski wrote:
> Found it.  It was a stupid mistake.  I made the get_sb function return 
> the same superblock when it was still get_sb_nodev.  When I switched it 
> to the proper get_sb_single I forgot to remove the code that returned 
> the old sb so it wasn't calling get_sb_single to increase the sb's usage 
> count.  Doh!

Cool! So when do we get a swappable initrd's/initramfs's?

-- wli

  reply	other threads:[~2003-11-29  9:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-29  5:24 Rootfs mounted from user space - problem with umount John Zielinski
2003-11-29  5:31 ` William Lee Irwin III
2003-11-29  6:14   ` John Zielinski
2003-11-29  6:21     ` William Lee Irwin III
2003-11-29  9:40       ` John Zielinski
2003-11-29  9:44         ` William Lee Irwin III [this message]
2003-11-29 20:02           ` John Zielinski
2003-11-29 20:20             ` John Zielinski
2003-11-29 20:25               ` William Lee Irwin III
2003-11-29 21:05                 ` John Zielinski
2003-11-29 21:17                   ` Sean Neakums
2003-11-29 21:42                     ` John Zielinski
2003-11-30  0:38                       ` [OT] " Sean Neakums
2003-11-29  5:38 ` Valdis.Kletnieks
2003-11-29  6:25   ` John Zielinski

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).