From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH 0/2] mtd: prepare for dynamically removed devices
Date: Thu, 22 Jun 2023 10:30:32 +0200 [thread overview]
Message-ID: <20230622103032.0febdb25@xps-13> (raw)
In-Reply-To: <20230620131905.648089-1-alexander.usyskin@intel.com>
Hi Alexander,
alexander.usyskin@intel.com wrote on Tue, 20 Jun 2023 16:19:03 +0300:
> Prepare mtd subsystem for devices that can be dynamically removed,
> like memory on PCIE card.
> Use refcount to prevent crashes when underlying device
> removed unexpectedly and reshuffle __get and __put functions
> to allow underlying device to clean it memory according to refcount.
>
> Alexander Usyskin (1):
> mtd: call external _get and _put in right order
>
> Tomas Winkler (1):
> mtd: use refcount to prevent corruption
>
> drivers/mtd/mtdcore.c | 86 ++++++++++++++++++++++-------------------
> drivers/mtd/mtdcore.h | 1 +
> drivers/mtd/mtdpart.c | 14 ++++---
> include/linux/mtd/mtd.h | 2 +-
> 4 files changed, 56 insertions(+), 47 deletions(-)
>
The idea is of course great, the implementation looks fine, but the
risk is too high at -rc7 so I'll take this at -rc1 for the next
release.
Thanks, Miquèl
prev parent reply other threads:[~2023-06-22 8:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 13:19 [PATCH 0/2] mtd: prepare for dynamically removed devices Alexander Usyskin
2023-06-20 13:19 ` [PATCH 1/2] mtd: use refcount to prevent corruption Alexander Usyskin
2023-07-12 14:14 ` Miquel Raynal
2023-07-14 16:10 ` Fabrizio Castro
2023-07-15 15:41 ` Miquel Raynal
2023-07-16 6:29 ` Usyskin, Alexander
2023-07-16 13:39 ` Miquel Raynal
2023-07-24 11:43 ` Usyskin, Alexander
2023-07-24 11:51 ` Miquel Raynal
2023-07-24 12:04 ` Usyskin, Alexander
2023-07-25 12:50 ` Usyskin, Alexander
2023-07-27 6:19 ` Miquel Raynal
2023-07-27 6:32 ` Winkler, Tomas
2023-07-27 6:55 ` Miquel Raynal
2023-06-20 13:19 ` [PATCH 2/2] mtd: call external _get and _put in right order Alexander Usyskin
2023-07-12 14:13 ` Miquel Raynal
2023-06-22 8:30 ` Miquel Raynal [this message]
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=20230622103032.0febdb25@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=alexander.usyskin@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=tomas.winkler@intel.com \
--cc=vigneshr@ti.com \
--cc=vitaly.lubart@intel.com \
/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