How does udev get devlink information for kernel device events?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I understand how the devlinks are created for linux devices by udev via udev rules. The one piece I don't understand is when the kernal emits an event that a particular device went down, how does udev apply the additional information to the event before sending out the udev event (ie the devlinks information)? Does it keep a database of this information somewhere? I have a situation where we have external enclosures containing scsi devices goes down, and a subset of the remove events is missing the devlinks information in the udev event even though the devlink was in place before they went down.
linux udev
asked Nov 30 at 21:22
bieno002
11
add a comment |
up vote
0
down vote
favorite
I understand how the devlinks are created for linux devices by udev via udev rules. The one piece I don't understand is when the kernal emits an event that a particular device went down, how does udev apply the additional information to the event before sending out the udev event (ie the devlinks information)? Does it keep a database of this information somewhere? I have a situation where we have external enclosures containing scsi devices goes down, and a subset of the remove events is missing the devlinks information in the udev event even though the devlink was in place before they went down.
linux udev
asked Nov 30 at 21:22
bieno002
11
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I understand how the devlinks are created for linux devices by udev via udev rules. The one piece I don't understand is when the kernal emits an event that a particular device went down, how does udev apply the additional information to the event before sending out the udev event (ie the devlinks information)? Does it keep a database of this information somewhere? I have a situation where we have external enclosures containing scsi devices goes down, and a subset of the remove events is missing the devlinks information in the udev event even though the devlink was in place before they went down.
linux udev
asked Nov 30 at 21:22
bieno002
11
I understand how the devlinks are created for linux devices by udev via udev rules. The one piece I don't understand is when the kernal emits an event that a particular device went down, how does udev apply the additional information to the event before sending out the udev event (ie the devlinks information)? Does it keep a database of this information somewhere? I have a situation where we have external enclosures containing scsi devices goes down, and a subset of the remove events is missing the devlinks information in the udev event even though the devlink was in place before they went down.
linux udev
linux udev
asked Nov 30 at 21:22
bieno002
11
asked Nov 30 at 21:22
bieno002
11
asked Nov 30 at 21:22
bieno002
11
asked Nov 30 at 21:22
bieno002
11
asked Nov 30 at 21:22
bieno002
11
11
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485260%2fhow-does-udev-get-devlink-information-for-kernel-device-events%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
