From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Linux Kernel readlink equivalent
Date: Fri, 30 Jan 2015 11:36:10 -0500 [thread overview]
Message-ID: <2817.1422635770@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 30 Jan 2015 11:02:01 -0500." <CABEmWXE3AKKEfPcw-nh0L_yV0NLyiXKSiDUULry3hE68HCpTKA@mail.gmail.com>
On Fri, 30 Jan 2015 11:02:01 -0500, David Legault said:
> the idea was to load a module passing the path as a module argument so I
> could access the underlying block device through the link without having to
> worry about the real block device path.
I hope you realize that scribbling on a block device without making *damned*
sure you're talking to the right *real* block device is just asking for
data corruption, right?
What problem are you *really* trying to solve here? It sounds like your design
has some serious layering violations....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150130/01e21729/attachment.bin
next prev parent reply other threads:[~2015-01-30 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 18:11 Linux Kernel readlink equivalent David Legault
2015-01-29 19:24 ` Valdis.Kletnieks at vt.edu
2015-01-29 19:37 ` Greg KH
2015-01-30 16:02 ` David Legault
2015-01-30 16:36 ` Valdis.Kletnieks at vt.edu [this message]
2015-01-30 17:17 ` Greg KH
2015-01-30 6:07 ` Aruna Hewapathirane
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=2817.1422635770@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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 NNTP newsgroup(s).