From: "Danilo Krummrich" <dakr@kernel.org>
To: "Priya Bala Govindasamy" <pgovind2@uci.edu>
Cc: <aliceryhl@google.com>, <daniel.almeida@collabora.com>,
<ojeda@kernel.org>, <boqun@kernel.org>, <gary@garyguo.net>,
<bjorn3_gh@protonmail.com>, <lossin@kernel.org>,
<a.hindborg@kernel.org>, <tmgross@umich.edu>, <tamird@kernel.org>,
<acourbot@nvidia.com>, <work@onurozkan.dev>, <me@kloenk.dev>,
<driver-core@lists.linux.dev>, <rust-for-linux@vger.kernel.org>,
<ardalan@uci.edu>, <zhiyunq@cs.ucr.edu>, <dzueck@uci.edu>
Subject: Re: [PATCH 1/1] rust: io: Fix `Region::drop` releasing nested resources from the wrong parent
Date: Wed, 30 Sep 2026 21:59:49 +0200 [thread overview]
Message-ID: <DLSX1QUUMSA4.C3YJIVTOC2P7@kernel.org> (raw)
In-Reply-To: <a71c5593cfc66e21f24d9c07ae3469fc4f8ea501.1788901318.git.pgovind2@uci.edu>
On Tue Sep 29, 2026 at 7:46 PM CEST, Priya Bala Govindasamy wrote:
> Fix this by storing a reference to the parent resource in `Region`.
> This ensures that the parent remains valid for the lifetime of the
> child region.
I Sashiko has a valid concern:
https://sashiko.dev/#/patchset/20260929174612.Jss-fw-sa4kdEy7Hk2_uC8PLsUpZ-K_gGWyuz4Qc6_k%40z
prev parent reply other threads:[~2026-09-30 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 22:57 [PATCH 0/1] rust: io: Fix `Region::drop` trying to release nested resources from the wrong parent Priya Bala Govindasamy
2026-09-29 17:46 ` [PATCH 0/1] rust: io: Fix `Region::drop` releasing " Priya Bala Govindasamy
2026-09-08 22:57 ` [PATCH 1/1] rust: io: Fix `Region::drop` trying to release " Priya Bala Govindasamy
2026-09-29 17:46 ` [PATCH 1/1] rust: io: Fix `Region::drop` releasing " Priya Bala Govindasamy
2026-09-30 19:59 ` Danilo Krummrich [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=DLSX1QUUMSA4.C3YJIVTOC2P7@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=ardalan@uci.edu \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=driver-core@lists.linux.dev \
--cc=dzueck@uci.edu \
--cc=gary@garyguo.net \
--cc=lossin@kernel.org \
--cc=me@kloenk.dev \
--cc=ojeda@kernel.org \
--cc=pgovind2@uci.edu \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
--cc=zhiyunq@cs.ucr.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.