summary refs log tree commit diff
path: root/fs/ext2
diff options
context:
space:
mode:
authorRussell King (Oracle) <rmk+kernel@armlinux.org.uk>2023-01-27 10:40:11 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-02-09 11:28:25 +0100
commit897dfd346223fed415d7d7e6644982166a60e727 (patch)
treed410691772bc57ad4319f8c97229562bad369f71 /fs/ext2
parent39708bc8da7858de0bed9b3a88b3beb1d1e0b443 (diff)
downloadlinux-897dfd346223fed415d7d7e6644982166a60e727.tar.gz
nvmem: core: fix registration vs use race
commit ab3428cfd9aa2f3463ee4b2909b5bb2193bd0c4a upstream.

The i.MX6 CPU frequency driver sometimes fails to register at boot time
due to nvmem_cell_read_u32() sporadically returning -ENOENT.

This happens because there is a window where __nvmem_device_get() in
of_nvmem_cell_get() is able to return the nvmem device, but as cells
have been setup, nvmem_find_cell_entry_by_node() returns NULL.

The occurs because the nvmem core registration code violates one of the
fundamental principles of kernel programming: do not publish data
structures before their setup is complete.

Fix this by making nvmem core code conform with this principle.

Fixes: eace75cfdcf7 ("nvmem: Add a simple NVMEM framework for nvmem providers")
Cc: stable@vger.kernel.org
Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Link: https://lore.kernel.org/r/20230127104015.23839-7-srinivas.kandagatla@linaro.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/ext2')
0 files changed, 0 insertions, 0 deletions