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
Add kernel support for the TP-LINK MR3040. #38
Closed
christianchristensen
wants to merge
1
commit into
freebsd:master
from
christianchristensen:tl-mr3040
Closed
Add kernel support for the TP-LINK MR3040. #38
christianchristensen
wants to merge
1
commit into
freebsd:master
from
christianchristensen:tl-mr3040
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
referenced
this pull request
in NextBSD/NextBSD
Sep 11, 2015
github-issue: #38 github-issue: freebsd#115 Signed-off By: Oliver Pinter <oliver.pinter@hardenedbsd.org> Signed-off By: Shawn Webb <shawn.webb@hardenedbsd.org> This commit removes the switch from arc4random to chacha20 and restores arc4random. Over the past few months, the HardenedBSD core team has been tracking kernel panics that only seemed to happen during periods of high load. The core team determined the work done for the ChaCha20 import was improperly done. This commit fixes the kernel panic. In order to do so, ChaCha20 support must be completely removed. The offending commit was a prerequisite for a proper ChaCha20 implementation. Offending commit: a222f4f ChaCha20 commits reverted by this commit: 1) 226292c 2) c44f9cc 3) 0d2bcc3 4) 91b00a2 5) 0556b25 6) efe9fbb 7) 43fdd9e 8) b090059 9) dd48dc2 10) dd48dc2 11) 6e9db36 12) 2eea13e 13) 01da3c8 14) 3627992 15) a0242df Importing ChaCha20 may be investigated again at a later date. Ideally, it ought to be done in a modular manner, similar to how Yarrow/Fortuna or the scheduler (4BSD, ULE) is done. The system administrator ought to be able to choose at kernel compile time which algorithm to use: arc4random or ChaCha20.
Author: imp Log: Submitted by: Chris Christensen cchristensen@llnw.com Added: |
uqs
pushed a commit
that referenced
this pull request
Mar 1, 2017
Submitted by: Chris Christensen <cchristensen@llnw.com> Pull Request: #38 git-svn-id: svn+ssh://svn.freebsd.org/base/head@314481 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
uqs
pushed a commit
that referenced
this pull request
Mar 1, 2017
Submitted by: Chris Christensen <cchristensen@llnw.com> Pull Request: #38
brooksdavis
pushed a commit
to CTSRD-CHERI/cheribsd
that referenced
this pull request
Mar 3, 2017
Submitted by: Chris Christensen <cchristensen@llnw.com> Pull Request: freebsd/freebsd-src#38
bdrewery
pushed a commit
to bdrewery/freebsd
that referenced
this pull request
Mar 9, 2017
Submitted by: Chris Christensen <cchristensen@llnw.com> Pull Request: freebsd#38 git-svn-id: svn+ssh://svn.freebsd.org/base/head@314481 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
mat813
pushed a commit
to mat813/freebsd
that referenced
this pull request
Apr 1, 2019
Log: ``` commit feb47278d7cffa8cf4bc8c8ff78047126fa41e82 (HEAD -> dev, origin/dev, origin/HEAD) Author: ngie-eign <1574099+ngie-eign@users.noreply.github.com> Date: Fri Mar 22 10:51:04 2019 -0700 Remove `FAIL` macro use for non-x86 architectures when testing `sysarch(2)` (freebsd#38) `FAIL()` does not support being called in the form noted in the test, which causes a test failure on non-x86 architectures. The alternatives (use `ADD_TEST_FAILURE()` or `GTEST_SKIP()`) would be misleading (in both cases), and in the case of `GTEST_SKIP()` is unavailable on the version of googletest packaged with capsicum-test. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com> commit 32ad0f3e4c11be7f7463d40eef8d4a78ac9f61a5 Author: Enji Cooper <yaneurabeya@gmail.com> Date: Fri Mar 15 20:01:56 2019 -0700 Fix `-Wunused-parameter` issues Remove variable declarations from functions/methods where the variable is not required. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com> commit 9437b4c550110200ef190ac39fb26c1d8fc55d9a Author: Enji Cooper <yaneurabeya@gmail.com> Date: Fri Mar 15 19:59:00 2019 -0700 Fix `-Wshadow` issues with `EXPECT_OPEN_OK(..)` macro * Wrap in do-while(0) block to avoid variable shadowing issue with multiple calls in the same function. * Prefix block local variables with `_` to try and avoid variable name clashes with values local to test methods. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com> commit adf4a21a233b5da5cac440f4006e258ffba09510 Author: Enji Cooper <yaneurabeya@gmail.com> Date: Fri Mar 15 19:55:00 2019 -0700 Fix `-Wmissing-variable-declarations` issue with `known_rights` global Staticize it since it is only used in the file. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com> ``` This merges a number of the outstanding changes made locally to ^/projects/capsicum-test that were accepted into the upstream project. The sync was done like so: ``` curl -L https://github.com/google/capsicum-test/tarball/dd7eac98c0cf | tar --strip-components=1 -xvzf - -C dist/ rm -Rf dist/*/ ``` 1. https://github.com/google/capsicum-test git-svn-id: https://svn.freebsd.org/base/vendor/google/capsicum-test@345715 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
uqs
pushed a commit
that referenced
this pull request
Apr 1, 2019
Log: ``` commit feb47278d7cffa8cf4bc8c8ff78047126fa41e82 (HEAD -> dev, origin/dev, origin/HEAD) Author: ngie-eign <1574099+ngie-eign@users.noreply.github.com> Date: Fri Mar 22 10:51:04 2019 -0700 Remove `FAIL` macro use for non-x86 architectures when testing `sysarch(2)` (#38) `FAIL()` does not support being called in the form noted in the test, which causes a test failure on non-x86 architectures. The alternatives (use `ADD_TEST_FAILURE()` or `GTEST_SKIP()`) would be misleading (in both cases), and in the case of `GTEST_SKIP()` is unavailable on the version of googletest packaged with capsicum-test. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com> commit 32ad0f3e4c11be7f7463d40eef8d4a78ac9f61a5 Author: Enji Cooper <yaneurabeya@gmail.com> Date: Fri Mar 15 20:01:56 2019 -0700 Fix `-Wunused-parameter` issues Remove variable declarations from functions/methods where the variable is not required. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com> commit 9437b4c550110200ef190ac39fb26c1d8fc55d9a Author: Enji Cooper <yaneurabeya@gmail.com> Date: Fri Mar 15 19:59:00 2019 -0700 Fix `-Wshadow` issues with `EXPECT_OPEN_OK(..)` macro * Wrap in do-while(0) block to avoid variable shadowing issue with multiple calls in the same function. * Prefix block local variables with `_` to try and avoid variable name clashes with values local to test methods. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com> commit adf4a21a233b5da5cac440f4006e258ffba09510 Author: Enji Cooper <yaneurabeya@gmail.com> Date: Fri Mar 15 19:55:00 2019 -0700 Fix `-Wmissing-variable-declarations` issue with `known_rights` global Staticize it since it is only used in the file. Signed-off-by: Enji Cooper <yaneurabeya@gmail.com> ``` This merges a number of the outstanding changes made locally to ^/projects/capsicum-test that were accepted into the upstream project. The sync was done like so: ``` curl -L https://github.com/google/capsicum-test/tarball/dd7eac98c0cf | tar --strip-components=1 -xvzf - -C dist/ rm -Rf dist/*/ ``` 1. https://github.com/google/capsicum-test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
xref: freebsd/freebsd-wifi-build#57