[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200228194456.8C147246B7@mail.kernel.org>
Date: Fri, 28 Feb 2020 19:44:55 +0000
From: Sasha Levin <sashal@...nel.org>
To: linux-kernel@...r.kernel.org
Cc: stable@...r.kernel.org
Subject: Re: [PATCH] loop: avoid EAGAIN, if offset or block_size are changed
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 5db470e229e2 ("loop: drop caches if offset or block_size are changed").
The bot has tested the following trees: v5.5.6, v5.4.22, v4.19.106, v4.14.171.
v5.5.6: Build OK!
v5.4.22: Build OK!
v4.19.106: Build OK!
v4.14.171: Failed to apply! Possible dependencies:
3148ffbdb916 ("loop: use killable lock in ioctls")
550df5fdacff ("loop: Push loop_ctl_mutex down to loop_set_status()")
757ecf40b7e0 ("loop: Push loop_ctl_mutex down to loop_set_fd()")
85b0a54a82e4 ("loop: Move loop_reread_partitions() out of loop_ctl_mutex")
a13165441d58 ("loop: Push lo_ctl_mutex down into individual ioctls")
c371077000f4 ("loop: Push loop_ctl_mutex down to loop_change_fd()")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
Powered by blists - more mailing lists