mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: cleanup filesystem core
Date: Wed, 15 Feb 2012 09:22:33 +0100	[thread overview]
Message-ID: <1329294165-12089-1-git-send-email-s.hauer@pengutronix.de> (raw)

This series cleans up the filesystem core. The great goal of this series is to
allow unmounting a fileystem by just unregistering the device.
unmount already goes down to unregister a device, but unmount also cleans up
the allocated ressources. We move the filesystem drivers/devices to their own
bus which allows us to clean up the resources in the busses remove function so
that a filesystem can be unmounted *and* cleaned up by unregistering the device.

With this series (and the preceding one) it's possible to call the 'usb' command
on a panda board multiple times without crashing barebox. I tested this with
the onboard USB network adapter and a USB flash drive with a FAT mounted.

Sascha

Sascha Hauer (12):
      add list_is_singular
      dos partitions: Do not register as fixed partitions
      fs: Store mtab entries in list
      fs: make locally used function get_mtab_entry_by_path static
      fs: Store mtab path in allocated string
      fs: remove unused function fsdev_get_mountpoint
      fs: simplify get_mtab_entry_by_path
      fs: remove only once used variable
      fs: remove fs devices list
      fs: put fs devices on its own bus
      fs: allow to mount on subdirectories
      devices: unregister children when unregistering a device

 commands/mount.c      |   17 ++--
 common/partitions.c   |    2 +-
 drivers/base/driver.c |   20 +++-
 fs/fs.c               |  233 ++++++++++++++++++++++--------------------------
 include/fs.h          |   19 ++---
 include/linux/list.h  |    9 ++
 6 files changed, 145 insertions(+), 155 deletions(-)

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2012-02-15  8:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15  8:22 Sascha Hauer [this message]
2012-02-15  8:22 ` [PATCH 01/12] add list_is_singular Sascha Hauer
2012-02-15  8:22 ` [PATCH 02/12] dos partitions: Do not register as fixed partitions Sascha Hauer
2012-02-15  8:22 ` [PATCH 03/12] fs: Store mtab entries in list Sascha Hauer
2012-02-15  8:22 ` [PATCH 04/12] fs: make locally used function get_mtab_entry_by_path static Sascha Hauer
2012-02-15  8:22 ` [PATCH 05/12] fs: Store mtab path in allocated string Sascha Hauer
2012-02-15  8:22 ` [PATCH 06/12] fs: remove unused function fsdev_get_mountpoint Sascha Hauer
2012-02-15  8:22 ` [PATCH 07/12] fs: simplify get_mtab_entry_by_path Sascha Hauer
2012-02-15  8:22 ` [PATCH 08/12] fs: remove only once used variable Sascha Hauer
2012-02-15  8:22 ` [PATCH 09/12] fs: remove fs devices list Sascha Hauer
2012-02-15  8:22 ` [PATCH 10/12] fs: put fs devices on its own bus Sascha Hauer
2012-02-15  8:22 ` [PATCH 11/12] fs: allow to mount on subdirectories Sascha Hauer
2012-02-15  8:22 ` [PATCH 12/12] devices: unregister children when unregistering a device Sascha Hauer

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=1329294165-12089-1-git-send-email-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.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