-
Notifications
You must be signed in to change notification settings - Fork 5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "ARM: 7668/1: fix memset-related crashes caused by recent GCC …
…(4.7.2) optimizations" This reverts commit 690c641. There have been various reports of FAT partition corruption following this commit. Reverting for now to see if things improve.
- Loading branch information
1 parent
79ec5aa
commit bb9948f
Showing
1 changed file
with
41 additions
and
44 deletions.
There are no files selected for viewing
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
bb9948f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given this was found to be buggy, shouldn't the upstream proper fix (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/arm/lib/memset.S?id=418df63adac56841ef6b0f1fcf435bc64d4ed177 as you noted in another spot) be pulled in instead of backing out to the prior also buggy state?
bb9948f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I second the last comment. The commit was fixed upstream with a second commit, and the complete proper fix should enable gcc 4.8 to be used to compile the kernel while also fixing potential issues with the current implementation.
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/arch/arm/lib/memset.S?id=455bd4c430b0c0a361f38e8658a0d6cb469942b5
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/arch/arm/lib/memset.S?id=418df63adac56841ef6b0f1fcf435bc64d4ed177