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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 1/30/25 3:58 PM, Andrew Morton wrote:
On Thu, 30 Jan 2025 02:02:38 -0500 "Michael S. Tsirkin" <mst@xxxxxxxxxx> 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@xxxxxxxxxx>
Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Cc: Michael S. Tsirkin <mst@xxxxxxxxxx>
Fixes: 0f3b1c40c652 ("fs/proc/vmcore: disallow vmcore modifications while the vmcore is open")
Signed-off-by: Bart Van Assche <bvanassche@xxxxxxx>

Acked-by: Michael S. Tsirkin <mst@xxxxxxxxxx>

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.




[Index of Archives]     [LM Sensors]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux