From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: How to receive notification of a new (disk) device being connected?
Date: Thu, 28 Apr 2016 20:55:12 +0300 [thread overview]
Message-ID: <57224E80.6060307@gmail.com> (raw)
In-Reply-To: <3df1c98b8135d4f64b0f9c3a8fa02df6@iam.tj>
28.04.2016 16:03, TJ пишет:
> I'm currently finalising a patch that adds key-file support to
> cryptodisk::cryptomount and luks.
>
> As well as being able to grub_device_iterate(hook,...) to search the
> existing devices for the key-file the code needs to wait for TIMEOUT
> seconds for additional (usually USB Mass Storage) devices to be
> connected and when they are search them for the key-file.
>
> Is there an existing mechanism to receive such notifications, or a
> blocking call that returns if a device is connected or a timeout is hit?
>
No. GRUB depends on firmware for disk access and not every firmware
supports hotplugging in the first place.
> Otherwise it looks like I'll have to track which devices are connected
> when the TIMEOUT loop is first entered, grub_sleep(), then
> grub_device_iterate() and see if the device list has any new entries.
>
> Secondly: am I correct to think using grub_search_fs_file(keyfile_name,
> variable_name, ...) is the correct way to search for the key-file across
> all devices, or do I need to use a specific hint type to indicate all
> devices should be searched?
>
Hints are used to optimize search - if you can guess firmware device
name, you avoid need to search across all devices. But it is in no way
mandatory, and search should work without it.
prev parent reply other threads:[~2016-04-28 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 13:03 How to receive notification of a new (disk) device being connected? TJ
2016-04-28 17:55 ` Andrei Borzenkov [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=57224E80.6060307@gmail.com \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.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).