[PATCH] procfs: Fix a locking bug in a vmcore_add_device_dump() error path
Bart Van Assche
bvanassche at acm.org
Thu Jan 30 17:02:08 PST 2025
On 1/30/25 3:58 PM, Andrew Morton wrote:
> On Thu, 30 Jan 2025 02:02:38 -0500 "Michael S. Tsirkin" <mst at 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 at redhat.com>
>>> Cc: Andrew Morton <akpm at linux-foundation.org>
>>> Cc: Michael S. Tsirkin <mst at redhat.com>
>>> Fixes: 0f3b1c40c652 ("fs/proc/vmcore: disallow vmcore modifications while the vmcore is open")
>>> Signed-off-by: Bart Van Assche <bvanassche at acm.org>
>>
>> Acked-by: Michael S. Tsirkin <mst at 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?
$ git log --after=2025-01-26 --before=2025-01-27 origin/master | \
grep 0f3b1c40c652
commit 0f3b1c40c65262a216fb459fd375f39442a5138b
Thanks,
Bart.
More information about the kexec
mailing list