From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-kselftest@vger.kernel.org, rppt@kernel.org, jack@suse.cz,
shuah@kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org, dmatlack@google.com,
pratyush@kernel.org, skhawaja@google.com
Subject: Re: [PATCH 1/2] liveupdate: prevent double management of files
Date: Tue, 24 Mar 2026 22:43:12 -0400 [thread overview]
Message-ID: <CA+CK2bCbgXHnZ0PhzfKE=NkykyqMKq6KBXW6JqMpq2R3k3RXDw@mail.gmail.com> (raw)
In-Reply-To: <20260324114021.f5546d2de5b6a2b0490f63cf@linux-foundation.org>
On Tue, Mar 24, 2026 at 2:40 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Tue, 24 Mar 2026 09:51:34 +0100 Christian Brauner <brauner@kernel.org> wrote:
>
> > > > So, I'm not happy about I_LUO_MANAGED. I don't think we need driver
> > > > specific stuff in struct inode and not in i_state. Track this in the
> > > > driver please. I don't want this precedent and I'd rather have you get
>
> Well dang, I just merged v2 but Christian wasn't cc'ed.
>
> > > I am planning to use an xarray in the next version.
>
> That's what v2 did, and I_LUO_MANAGED has gone away.
>
> Christian, does v2 look OK? It's at
> https://lkml.kernel.org/r/20260323203145.148057-1-pasha.tatashin@soleen.com
Yes, v2 is fine. Here, we discussed about the previous approach, this
is one of the reason why v2 exists: not to modify inode, and also not
to rely on inode being different for every preserved file.
Thanks,
Pasha
>
>
next prev parent reply other threads:[~2026-03-25 2:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 17:58 [PATCH 0/2] liveupdate: prevent double management of files Pasha Tatashin
2026-03-21 17:58 ` [PATCH 1/2] " Pasha Tatashin
2026-03-22 1:04 ` Pasha Tatashin
2026-03-23 11:55 ` Christian Brauner
2026-03-23 13:18 ` Pasha Tatashin
2026-03-24 8:51 ` Christian Brauner
2026-03-24 18:40 ` Andrew Morton
2026-03-25 2:43 ` Pasha Tatashin [this message]
2026-03-21 17:58 ` [PATCH 2/2] selftests: liveupdate: add test for double preservation Pasha Tatashin
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='CA+CK2bCbgXHnZ0PhzfKE=NkykyqMKq6KBXW6JqMpq2R3k3RXDw@mail.gmail.com' \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=dmatlack@google.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=skhawaja@google.com \
--cc=viro@zeniv.linux.org.uk \
/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