Skip to content
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/modules-closure.sh: fix the modules closure #66235

Closed
wants to merge 1 commit into from

Conversation

xaverdh
Copy link
Contributor

@xaverdh xaverdh commented Aug 6, 2019

Prior to this commit the modules closure could reference nonsensical
pieces of data in to form of module parameters. These were treated as
separate modules.

Motivation for this change

resolving #57421

Things done

I tested this on my own device, but since this touches a core part, it should probably get some real testing.

@infinisil
Copy link
Member

Can you add a comment in the code explaining what that regex does? And the commit message could explain why the change was necessary and e.g. what new parts the regex doesn't include/newly includes.

@xaverdh
Copy link
Contributor Author

xaverdh commented Sep 22, 2019

Should I include a reference to the source at kernel.org in the commit message?

@xaverdh
Copy link
Contributor Author

xaverdh commented Sep 22, 2019

Also I had to touch that line some more, to place the comment somewhere sane. While doing that, I noticed, that I don't understand how the exit status test is supposed to work (even in the original version). I think its supposed to cover the case where modprobe exists with nonzero exit status, but that will get swallowed by the pipe.

@xaverdh
Copy link
Contributor Author

xaverdh commented Sep 26, 2019

I opened a separate pr which should fix the check for missing modules as well.

Prior to this commit the modules closure could reference nonsensical
pieces of data in to form of module parameters. These were treated
as seperate modules.

"modprobe --show-depends" outputs a line of the form
"insmod module_name module_args", we are only interested in the
module name, so we extract it with sed.
@xaverdh
Copy link
Contributor Author

xaverdh commented Dec 9, 2019

Ping
Is there something more I should do?
Would be cool to get one of these prs merged.

@infinisil
Copy link
Member

Looks good to me, though I haven't tested it. How does this PR compare to the other one?

@xaverdh
Copy link
Contributor Author

xaverdh commented Dec 10, 2019

The second one

Also fixes a bug in the original implementation where the check for missing modules did not work as indended (the exit status of
modprobe was ignored due to a pipe).

@stale
Copy link

stale bot commented Jun 7, 2020

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

  1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
  2. Ask on the NixOS Discourse.
  3. Ask on the #nixos channel on irc.freenode.net.

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 7, 2020
@xaverdh
Copy link
Contributor Author

xaverdh commented Aug 13, 2020

closed in favour of #92081

@xaverdh xaverdh closed this Aug 13, 2020
@xaverdh xaverdh deleted the fix-modules-closure branch August 13, 2020 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md 10.rebuild-darwin: 0 10.rebuild-linux: 0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants