From: Andrew Norrie <andrew.norrie@cgg.com>
To: <jaegeuk@kernel.org>
Cc: <axboe@kernel.dk>, <bvanassche@acm.org>,
<linux-block@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
Andrew Norrie <andrew.norrie@cgg.com>
Subject: Re: loop: avoid EAGAIN, if offset or block_size are changed
Date: Mon, 18 Nov 2019 11:36:16 -0700 [thread overview]
Message-ID: <1574102176-23804-1-git-send-email-andrew.norrie@cgg.com> (raw)
In-Reply-To: <20190617210848.GB57907@jaegeuk-macbookpro.roam.corp.google.com>
Any chance to get a review on this patch?
We're running Singularity containers in an mpi environment where multiple
concurrent container image loop mounts occur and we hit this issue as reported
to Sylabs by us here:
https://github.com/sylabs/singularity/issues/3860
It is affecting our production.
This email and any accompanying attachments are confidential. If you received this email by mistake, please delete
it from your system. Any review, disclosure, copying, distribution, or use of the email by others is strictly prohibited.
next prev parent reply other threads:[~2019-11-18 18:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 0:47 [PATCH] loop: avoid EAGAIN, if offset or block_size are changed Jaegeuk Kim
2019-05-18 0:53 ` [PATCH v2] " Jaegeuk Kim
2019-06-17 21:08 ` [f2fs-dev] " Jaegeuk Kim
2019-11-18 18:36 ` Andrew Norrie [this message]
2019-11-19 4:00 ` Greg KH
2019-11-19 23:40 ` [PATCH v2] " Bart Van Assche
2019-11-25 17:59 ` Jaegeuk Kim
2019-11-25 18:35 ` Bart Van Assche
2019-11-25 19:22 ` Jaegeuk Kim
2019-11-25 19:41 ` Bart Van Assche
2019-11-25 22:27 ` Bart Van Assche
2019-11-26 18:29 ` Jaegeuk Kim
2019-11-26 18:59 ` Bart Van Assche
2019-11-26 22:32 ` Jaegeuk Kim
2019-11-26 22:54 ` Bart Van Assche
2019-11-27 0:04 ` Jaegeuk Kim
2019-11-27 0:26 ` Bart Van Assche
2019-11-27 1:09 ` Jaegeuk Kim
2019-11-27 16:35 ` Bart Van Assche
2019-11-27 18:17 ` Jaegeuk Kim
2019-11-27 18:18 ` [f2fs-dev] [PATCH v3] " Jaegeuk Kim
2019-11-27 18:54 ` Bart Van Assche
2020-02-19 19:58 ` Andrew Norrie
2020-03-05 21:04 ` [PATCH] " 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=1574102176-23804-1-git-send-email-andrew.norrie@cgg.com \
--to=andrew.norrie@cgg.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).