New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kernel module IOCTL numbers should be generated with <ioctl.h> macros #249
Labels
Comments
Looking at this issue further, it seems the IOCTL numbers are defined using the correct macros (in |
BrentHoltsclaw
added a commit
to BrentHoltsclaw/chipsec
that referenced
this issue
Jan 7, 2019
changed drivers/linux/include/chipsec.h to start from 'C' added logic to compute ioctl base based upon changes to chipsec.h above
BrentHoltsclaw
added a commit
to BrentHoltsclaw/chipsec
that referenced
this issue
Jan 7, 2019
changed drivers/linux/include/chipsec.h to start from 'C' added logic to compute ioctl base based upon changes to chipsec.h above
BrentHoltsclaw
added a commit
to BrentHoltsclaw/chipsec
that referenced
this issue
Jan 14, 2019
changed drivers/linux/include/chipsec.h to start from 'C' added logic to compute ioctl base based upon changes to chipsec.h above
ErikBjorge
pushed a commit
that referenced
this issue
Jan 17, 2019
changed drivers/linux/include/chipsec.h to start from 'C' added logic to compute ioctl base based upon changes to chipsec.h above
This should be fixed and merged within #506. Please reopen the issue if there are farther concerns. Thanks |
0xfede7c8
pushed a commit
to 0xfede7c8/chipsec
that referenced
this issue
Jul 16, 2019
changed drivers/linux/include/chipsec.h to start from 'C' added logic to compute ioctl base based upon changes to chipsec.h above
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Best practices for kernel modules dictate that IOCTL numbers should be generated with the _IO, _IOR, _IOW, _IOWR macros rather than laid down sequentially from 0.
This is partially for versioning purposes and partially to ensure that sending an IOCTL to the wrong device does not silently succeed.
The text was updated successfully, but these errors were encountered: