diff options
| author | John Stultz <john.stultz@linaro.org> | 2011-05-06 17:26:25 -0700 |
|---|---|---|
| committer | John Stultz <john.stultz@linaro.org> | 2011-05-06 18:02:00 -0700 |
| commit | 2f5c4fe8f9811152d69ef5cd020e095a1f84ca65 (patch) | |
| tree | 8a761a6772cbeae7d9661b29e55a7a9965719178 /drivers/rtc/rtc-ds1305.c | |
| parent | a015dbc110a97ed3147546a9c914f18f71d798d0 (diff) | |
| download | linux-stable-2f5c4fe8f9811152d69ef5cd020e095a1f84ca65.tar.gz linux-stable-2f5c4fe8f9811152d69ef5cd020e095a1f84ca65.tar.bz2 linux-stable-2f5c4fe8f9811152d69ef5cd020e095a1f84ca65.zip | |
rtc: max8925: Initialize drvdata before registering device
Commit f44f7f96a20 ("RTC: Initialize kernel state from RTC") uncovered
an issue in a number of RTC drivers, where the drivers call
rtc_device_register before initializing the device or platform drvdata.
This frequently results in null pointer dereferences when the
rtc_device_register immediately makes use of the rtc device, calling
rtc_read_alarm.
The solution is to ensure the drvdata is initialized prior to registering
the rtc device.
CC: Wolfram Sang <w.sang@pengutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: rtc-linux@googlegroups.com
Signed-off-by: John Stultz <john.stultz@linaro.org>
Diffstat (limited to 'drivers/rtc/rtc-ds1305.c')
0 files changed, 0 insertions, 0 deletions