[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZaZo98YNJNilBSVI@sashalap>
Date: Tue, 16 Jan 2024 06:31:03 -0500
From: Sasha Levin <sashal@...nel.org>
To: Amir Goldstein <amir73il@...il.com>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Miklos Szeredi <mszeredi@...hat.com>, Ian Kent <raven@...maw.net>,
Christian Brauner <brauner@...nel.org>, viro@...iv.linux.org.uk,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 6.1 12/14] add unique mount ID
On Tue, Jan 16, 2024 at 11:04:12AM +0200, Amir Goldstein wrote:
>On Tue, Jan 16, 2024 at 1:46 AM Sasha Levin <sashal@...nel.org> wrote:
>>
>> From: Miklos Szeredi <mszeredi@...hat.com>
>>
>> [ Upstream commit 98d2b43081972abeb5bb5a087bc3e3197531c46e ]
>>
>> If a mount is released then its mnt_id can immediately be reused. This is
>> bad news for user interfaces that want to uniquely identify a mount.
>>
>
>Sasha,
>
>This is a new API, not a bug fix.
>Maybe AUTOSEL was triggered by the words "This is bad news for user...."?
>
>You have also selected this to other 6.*.y kernels.
Ack, I'll drop it from everywhere. Thanks!
--
Thanks,
Sasha
Powered by blists - more mailing lists