Re: [PATCH] procfs: Fix a locking bug in a vmcore_add_device_dump() error path

["Michael S. Tsirkin" <mst@redhat.com>]

On Thu, Jan 30, 2025 at 05:20:53PM -0800, Andrew Morton wrote:
> On Thu, 30 Jan 2025 17:02:08 -0800 Bart Van Assche <bvanassche@acm.org> wrote:
> 
> > On 1/30/25 3:58 PM, Andrew Morton wrote:
> > > On Thu, 30 Jan 2025 02:02:38 -0500 "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > > 
> > >> On Wed, Jan 29, 2025 at 02:20:03PM -0800, Bart Van Assche wrote:
> > >>> Unlock vmcore_mutex when returning -EBUSY.
> > >>>
> > >>> Cc: David Hildenbrand <david@redhat.com>
> > >>> Cc: Andrew Morton <akpm@linux-foundation.org>
> > >>> Cc: Michael S. Tsirkin <mst@redhat.com>
> > >>> Fixes: 0f3b1c40c652 ("fs/proc/vmcore: disallow vmcore modifications while the vmcore is open")
> > >>> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> > >>
> > >> Acked-by: Michael S. Tsirkin <mst@redhat.com>
> > > 
> > > This applies to patches which are in linux-next via your tree (I
> > > think), so I'll take the above to mean "thanks, applied" ;)
> > 
> > Is my understanding correct that the commit fixed by this patch made it
> > into Linus' tree a few days ago?
> > 
> 
> Ah, OK, thanks, grabbed.
> 
> (So that's what "git pull" does.  I'll have to write that down.)

:)
Thanks.