[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <26feedff-0fb4-01db-c809-81c932336b47@redhat.com>
Date: Sun, 15 Aug 2021 15:57:24 +0200
From: Hans de Goede <hdegoede@...hat.com>
To: Pavel Machek <pavel@....cz>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Sudip Mukherjee <sudipm.mukherjee@...il.com>
Subject: Re: [PATCH 5.10 12/19] vboxsf: Make vboxsf_dir_create() return the
handle for the created file
Hi,
On 8/13/21 9:31 PM, Pavel Machek wrote:
> Hi!
>
>> commit ab0c29687bc7a890d1a86ac376b0b0fd78b2d9b6 upstream
>>
>> Make vboxsf_dir_create() optionally return the vboxsf-handle for
>> the created file. This is a preparation patch for adding atomic_open
>> support.
>
> Follow up commits using this functionality are in 5.13 but not in
> 5.10, so I believe we don't need this in 5.10, either?
>
> (Plus someone familiar with the code should check if we need "vboxsf:
> Honor excl flag to the dir-inode create op" in 5.10; it may have same
> problem).
Actually those follow up commits fix an actual bug, so I was expecting
the person who did the backport to also submit the rest of the set.
FWIW having these patches in but not the cannot hurt.
Hopefully the rest applies cleanly, I don't know.
To be clear I'm talking about also adding the following to patches
to 5.10.y:
02f840f90764 ("vboxsf: Add vboxsf_[create|release]_sf_handle() helpers")
52dfd86aa568 ("vboxsf: Add support for the atomic_open directory-inode op")
I have no idea of these will apply cleanly.
Regards,
Hans
Powered by blists - more mailing lists