Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
NuttX RTOS
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
f4grx
NuttX RTOS
Commits
26d40fa8
Commit
26d40fa8
authored
9 years ago
by
xuhang
Committed by
Gregory Nutt
9 years ago
Browse files
Options
Downloads
Patches
Plain Diff
drivers/usbhost/hid_parser.c: Wrong size used in memcpy()
parent
aad3b013
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
ChangeLog
+2
-0
2 additions, 0 deletions
ChangeLog
drivers/usbhost/hid_parser.c
+1
-3
1 addition, 3 deletions
drivers/usbhost/hid_parser.c
with
3 additions
and
3 deletions
ChangeLog
+
2
−
0
View file @
26d40fa8
...
...
@@ -11358,3 +11358,5 @@
* arch/arm/src/samv7/chip: Add an AFEC header file (2016-01-25).
* net/iob: iob_alloc_qentry() has the same issues as did iob_alloc()
fixed on 2016-01-23. (2016-01-26).
* drivers/usbhost/hid_parser.c: Wrong size used in memcpy(). From Hang
Xu (2016-01-25).
This diff is collapsed.
Click to expand it.
drivers/usbhost/hid_parser.c
+
1
−
3
View file @
26d40fa8
...
...
@@ -139,9 +139,7 @@ int hid_parsereport(FAR const uint8_t *report, int rptlen,
return
-
E2BIG
;
}
memcpy
((
currstate
+
1
),
currstate
,
sizeof
(
struct
hid_rptitem_s
));
memcpy
((
currstate
+
1
),
currstate
,
sizeof
(
struct
hid_state_s
));
currstate
++
;
break
;
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment