From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Okazaki <dtokazaki@google.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
kernel-team@android.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] eeprom: at24: fix memory corruption race condition
Date: Tue, 23 Apr 2024 10:15:18 +0200 [thread overview]
Message-ID: <171386010055.10921.7297413066417044638.b4-ty@linaro.org> (raw)
In-Reply-To: <20240422174337.2487142-1-dtokazaki@google.com>
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
On Mon, 22 Apr 2024 17:43:36 +0000, Daniel Okazaki wrote:
> If the eeprom is not accessible, an nvmem device will be registered, the
> read will fail, and the device will be torn down. If another driver
> accesses the nvmem device after the teardown, it will reference
> invalid memory.
>
> Move the failure point before registering the nvmem device.
>
> [...]
Applied, thanks!
[1/1] eeprom: at24: fix memory corruption race condition
commit: f42c97027fb75776e2e9358d16bf4a99aeb04cf2
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
next prev parent reply other threads:[~2024-04-23 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 17:43 [PATCH v3] eeprom: at24: fix memory corruption race condition Daniel Okazaki
2024-04-22 22:09 ` Greg Kroah-Hartman
2024-04-23 8:14 ` Bartosz Golaszewski
2024-04-23 6:15 ` Markus Elfring
2024-04-23 8:13 ` Bartosz Golaszewski
2024-04-23 8:15 ` Bartosz Golaszewski [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-19 19:04 [PATCH v2] " Markus Elfring
2024-04-19 19:12 ` [PATCH v3] " Daniel Okazaki
2024-04-20 6:15 ` Greg Kroah-Hartman
2024-04-20 9:11 ` Markus Elfring
2024-04-20 10:04 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171386010055.10921.7297413066417044638.b4-ty@linaro.org \
--to=brgl@bgdev.pl \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=dtokazaki@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).