From: Stanislav Meduna <stano@meduna.org>
To: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] umount leaks /dev/flash/ device slots
Date: Fri, 04 Sep 2009 09:41:00 -0000 [thread overview]
Message-ID: <4AA0E0BF.4010405@meduna.org> (raw)
Hi,
it looks like the mount/umount leak slots in the flashiodev_table.
I.e. if I repeatedly do mount/umount /dev/flash/fis/fs, each
mount allocates one slot, but umount fails to free it. After some
time all the CYGNUM_IO_FLASH_BLOCK_DEVICES slots of flashiodev_table
are filled with a reference to this partition and further mounts fail.
Flash is special in that a reference that is no more needed
has to be cleaned by calling CYG_IO_SET_CONFIG_CLOSE. My guess
is that the umount is not doing this, but I know these
layers too little to be able to quickly find the problem.
Thanks
--
Stano
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2009-09-04 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 9:41 Stanislav Meduna [this message]
2009-09-04 10:11 ` [ECOS] CPULoad on i386 Jim Bradleigh
2009-09-04 15:09 ` Jim Bradleigh
2013-11-14 10:15 ` [ECOS] Re: umount leaks /dev/flash/ device slots Daniel Zebralla
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=4AA0E0BF.4010405@meduna.org \
--to=stano@meduna.org \
--cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).