From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, stable@vger.kernel.org
Cc: <stable@vger.kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Cc: Bart Van Assche <bvanassche@acm.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] loop: avoid EAGAIN, if offset or block_size are changed
Date: Fri, 28 Feb 2020 19:44:55 +0000 [thread overview]
Message-ID: <20200228194456.8C147246B7@mail.kernel.org> (raw)
In-Reply-To: <20200228043820.169288-1-jaegeuk@kernel.org>
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
next prev parent reply other threads:[~2020-02-28 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 4:38 [PATCH] loop: avoid EAGAIN, if offset or block_size are changed Jaegeuk Kim
2020-02-28 4:38 ` [f2fs-dev] " Jaegeuk Kim
2020-02-28 19:44 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-18 0:47 Jaegeuk Kim
2020-03-05 21:04 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200228194456.8C147246B7@mail.kernel.org \
--to=sashal@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.