From: WyoFlippa <wyoflippa@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Kernel drivers and IOCTLs
Date: Tue, 21 Jan 2020 22:27:01 -0600 [thread overview]
Message-ID: <8969dfce-a295-c351-201c-4d8a0e90ac58@gmail.com> (raw)
Hi,
I'm working on a driver that would verify a Linux or U-Boot image is
secure and I need to pass parameters such as the public key, starting
address, etc. I'd heard in talking to developers that IOCTLs are frowned
upon. I also found this article that seems to indicate that using sysfs
or proc is a better way to go.
https://www.linuxjournal.com/article/8110
but then I see this article from 2013 which is more recent than the article.
https://www.kernel.org/doc/html/latest/process/botching-up-ioctls.html
So are IOCTLs discouraged or not?
Thanks,
TW
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2020-01-22 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 4:27 WyoFlippa [this message]
2020-01-22 19:04 ` Kernel drivers and IOCTLs Greg KH
2020-01-23 16:49 ` Valdis Klētnieks
2020-02-05 2:57 ` WyoFlippa
2020-02-05 4:01 ` Valdis Klētnieks
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=8969dfce-a295-c351-201c-4d8a0e90ac58@gmail.com \
--to=wyoflippa@gmail.com \
--cc=kernelnewbies@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).