Skip to content

Ieee80215 bug fix #31908

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

Merged
merged 6 commits into from
Feb 3, 2021
Merged

Conversation

tbursztyka
Copy link
Collaborator

No description provided.

@tbursztyka tbursztyka added bug The issue is a bug, or the PR is fixing a bug area: IEEE 802.15.4 labels Feb 3, 2021
@tbursztyka tbursztyka added this to the v2.5.0 milestone Feb 3, 2021
@tbursztyka tbursztyka requested a review from jukkar as a code owner February 3, 2021 09:15
@tbursztyka tbursztyka requested review from nashif and ceolin February 3, 2021 09:15
@tbursztyka tbursztyka force-pushed the ieee80215_bug_fix branch 2 times, most recently from 4833bcb to 5f65dee Compare February 3, 2021 13:22
@zephyrbot zephyrbot requested a review from pfalcon February 3, 2021 15:25
Tomasz Bursztyka added 6 commits February 3, 2021 18:34
All addressing mode but IEEE802154_ADDR_MODE_NONE should have a valid
address. If not, the frame is invalid.

Signed-off-by: Tomasz Bursztyka <[email protected]>
Not validating this length could lead to integer underflow and memory
corruption.

Signed-off-by: Tomasz Bursztyka <[email protected]>
In case the very first fragment holds all the data already.

Signed-off-by: Tomasz Bursztyka <[email protected]>
Though ACK frames are not meant to reach L2 (drivers must ensure this
never happens), let's "re-enforce" the L2 by dropping them.

Signed-off-by: Tomasz Bursztyka <[email protected]>
In case the current packet is the same as the cached one, let's not
unreference it while clearing the cache.

Signed-off-by: Tomasz Bursztyka <[email protected]>
Bogus fragmented packet could be sent without a FRAG1 fragment and hit
reassembly. Let's make sure this does not happen.

Signed-off-by: Tomasz Bursztyka <[email protected]>
@nashif nashif closed this Feb 3, 2021
@nashif nashif reopened this Feb 3, 2021
@nashif nashif merged commit a980762 into zephyrproject-rtos:master Feb 3, 2021
@tbursztyka tbursztyka deleted the ieee80215_bug_fix branch February 16, 2021 13:23
@zephyrbot
Copy link
Collaborator

The backport to v1.14-branch failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.14-branch v1.14-branch
# Navigate to the new working tree
cd .worktrees/backport-v1.14-branch
# Create a new branch
git switch --create backport-31908-to-v1.14-branch
# Cherry-pick the merged commits of this pull request and resolve the conflicts
git cherry-pick a980762f70d7048825e6ce9e42ceb6b5f87a5e44~6..a980762f70d7048825e6ce9e42ceb6b5f87a5e44
# Push it to GitHub
git push --set-upstream origin backport-31908-to-v1.14-branch
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.14-branch

Then, create a pull request where the base branch is v1.14-branch and the compare/head branch is backport-31908-to-v1.14-branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: IEEE 802.15.4 area: Networking bug The issue is a bug, or the PR is fixing a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants