mtd: Create gluebi mtdblocks if CONFIG_FTL is not enabled #209
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.
WI: AB#3024196
Bluefin devices expect to mount mtdblock devices created by gluebi at runtime, but cfd7c9d prevents gluebi from creating these mtdblock devices as a mitigation to a NULL pointer dereference caused by FTL notifier. As a workaround, this commit adds a check for
CONFIG_FTLbefore doing so, keeping the solution intact ifCONFIG_FTLis enabled, while allowing the creation of gluebi mtdblock devices ifCONFIG_FTLis not enabled.Testing: Built and deployed kernel with changes on cDAQ-9189, verified that mtdblocks are enumerated for gluebi mtd partitions when
CONFIG_FTLis not enabled.