From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Alexander Schmidt <alexs@linux.vnet.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Frank Haverkamp <haver@linux.vnet.ibm.com>
Subject: Re: [RFC] [PATCH] UBI: rewrite of sysfs.c
Date: Wed, 14 Mar 2007 11:23:41 +0200 [thread overview]
Message-ID: <45F7BF1D.5020405@nokia.com> (raw)
In-Reply-To: <200703131610.20161.alexs@linux.vnet.ibm.com>
Alexander Schmidt wrote:
> Hi,
>
> I rewrote the sysfs interface to use struct device instead of struct
> class_device. This implies an interface change, as sysfs files are now
> ordered in a different manner:
>
> /sys/class/ubi/ubiX/ for device files
> /sys/class/ubi/ubiX_Y/ for volumes
>
> Before we had
>
> /sys/class/ubi/ubiX/ for device files
> /sys/class/ubi/ubiX/Y/ for volumes
>
> Please let me know if you got any objections on this or if you have
> proposals for a better implementation.
Alexander, may I please ask you to to the following experiments with your new changes:
Experiment 1: open sysfs file, and make sure UBI module refcount is increased.
lsmod will help. Please, check this with a UBI device's file and a UBI volume's
file.
Experiment 2: write a program which opens any sysfs file of volume, e.g.,
/sys/class/ubi/ubi0_0/alignment, and keeps it open. Do not close it. Then
remove the corresponding volume (volume 0). Make sure you delete the volume
and do not crash.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2007-03-14 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 15:10 [RFC] [PATCH] UBI: rewrite of sysfs.c Alexander Schmidt
2007-03-13 16:38 ` Artem Bityutskiy
2007-03-13 16:42 ` Artem Bityutskiy
2007-03-14 8:24 ` Frank Haverkamp
2007-03-14 8:32 ` Artem Bityutskiy
2007-03-16 22:25 ` Thomas Gleixner
2007-03-14 9:23 ` Artem Bityutskiy [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=45F7BF1D.5020405@nokia.com \
--to=artem.bityutskiy@nokia.com \
--cc=alexs@linux.vnet.ibm.com \
--cc=haver@linux.vnet.ibm.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.