From: Jens Axboe <axboe@suse.de>
To: Adam Schrotenboer <ajschrotenboer@lycosmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Loop broken again (2.4.6-ac4)
Date: Fri, 20 Jul 2001 22:35:02 +0200 [thread overview]
Message-ID: <20010720223502.B3969@suse.de> (raw)
In-Reply-To: <3B57A811.9030408@lycosmail.com>
In-Reply-To: <3B57A811.9030408@lycosmail.com>
On Thu, Jul 19 2001, Adam Schrotenboer wrote:
> Jens,
>
> Remember several weeks ago when I mentioned a problem w/ ridicyulous
> mod-use counts w/ loop.o???
> Well, it's back again 2.4.5-ac19 (IIRC) worked fine.
>
> Basically, the result of attempting sudo losetup -d /dev/loop0 is the
> following
>
> ioctl LOOP_CLR_FD Device or resource busy
>
> strace shows EBUSY
>
> lsmod shows a use count of 563.
I've had no time to look at this, so feel free to dig in and find out
why the usage count is getting screwed... It's probably just a silly
little bug somewhere, I'm guessing a one-liner fix :-)
--
Jens Axboe
prev parent reply other threads:[~2001-07-20 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-20 3:40 Loop broken again (2.4.6-ac4) Adam Schrotenboer
2001-07-20 20:35 ` Jens Axboe [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=20010720223502.B3969@suse.de \
--to=axboe@suse.de \
--cc=ajschrotenboer@lycosmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox