From: Chris Ball <cjb@laptop.org>
To: jongman.heo@samsung.com
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: Erasing MMC partition from kernel module, what's best way to do that?
Date: Wed, 11 Jan 2012 14:19:55 -0500 [thread overview]
Message-ID: <m24nw2f3ms.fsf@bob.laptop.org> (raw)
In-Reply-To: <21845361.155711326104068000.JavaMail.weblogic@epml02> (JONGMAN HEO's message of "Mon, 09 Jan 2012 10:14:28 +0000 (GMT)")
Hi,
On Mon, Jan 09 2012, JONGMAN HEO wrote:
> Hi all,
> Please excuse me, I have some noob question regarding MMC.
>
> I'd like to erase(discard) certain MMC partition from kernel space
> (i.e. kernel module).
> I know this is quite ugly design, but I have no choice but to
> implement the feature (erasing given MMC partition) within kernel
> space for other reasons.
>
> Assume /dev/mmcblk0p2 needs to be erased.
>
> First, I tried to use BLKDISCARD ioctl. From user space, it works.
> In kernel space, I had to use ugly code, like set_fs(), filp_open(),
> etc in order to access "/dev/mmcblk0p2" device.
> I stuck at sys_ioctl(), which is not exported symbol so that I
> couldn't use the sys_ioctl() from my module for the BLKDISCARD ioctl.
>
> Alternatively, I want to make a new exported API to execute the
> discard request for "/dev/mmcblk0p2" device (like
> mmc_test_area_erase() in mmc_test.c).
> Here, it seems that I need to get "struct mmc_card *card" instance,
> which is a first parameter of mmc_erase().
>
> How can I get the "card" instance for current MMC device? Is there any
> way to do that?
I don't think we'll be interested in helping you with this -- as you
say, this is a very ugly design, and we already have the proper
userspace solution.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2012-01-11 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 10:14 Erasing MMC partition from kernel module, what's best way to do that? JONGMAN HEO
2012-01-11 19:19 ` Chris Ball [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=m24nw2f3ms.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=jongman.heo@samsung.com \
--cc=linux-mmc@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 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.