From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
To: "Frédéric Danis" <frederic.danis@collabora.com>,
linux-um@lists.infradead.org
Subject: Re: [PATCH] um: Fix WRITE_ZEROES in the UBD Driver
Date: Tue, 25 Jan 2022 17:56:17 +0000 [thread overview]
Message-ID: <8de3a6c3-b2fd-648e-ac5f-a27da2d326db@cambridgegreys.com> (raw)
In-Reply-To: <20220125171405.163362-1-frederic.danis@collabora.com>
On 25/01/2022 17:14, Frédéric Danis wrote:
> Call to fallocate with FALLOC_FL_PUNCH_HOLE on a device backed by a sparse
> file can end up by missing data, zeroes data range, if the underlying file
> is used with a tool like bmaptool which will referenced only used spaces.
Can you elaborate on when do you miss data.
A file with a hole created using FALLOC_FL_PUNCH_HOLE when reading from
the hole should return zeroes.
If it returns anything else or if the zeroed range exceeds the one
specified in falloc - that is an underlying fs bug.
>
> Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>
> ---
> arch/um/drivers/ubd_kern.c | 8 +++++++-
> arch/um/include/shared/os.h | 1 +
> arch/um/os-Linux/file.c | 9 +++++++++
> 3 files changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/arch/um/drivers/ubd_kern.c b/arch/um/drivers/ubd_kern.c
> index 69d2d0049a61..b03269faef71 100644
> --- a/arch/um/drivers/ubd_kern.c
> +++ b/arch/um/drivers/ubd_kern.c
> @@ -1526,13 +1526,19 @@ static void do_io(struct io_thread_req *req, struct io_desc *desc)
> }
> break;
> case REQ_OP_DISCARD:
> - case REQ_OP_WRITE_ZEROES:
> n = os_falloc_punch(req->fds[bit], off, len);
> if (n) {
> req->error = map_error(-n);
> return;
> }
> break;
> + case REQ_OP_WRITE_ZEROES:
> + n = os_falloc_zeroes(req->fds[bit], off, len);
> + if (n) {
> + req->error = map_error(-n);
> + return;
> + }
> + break;
> default:
> WARN_ON_ONCE(1);
> req->error = BLK_STS_NOTSUPP;
> diff --git a/arch/um/include/shared/os.h b/arch/um/include/shared/os.h
> index 00214059d9ec..fafde1d5416e 100644
> --- a/arch/um/include/shared/os.h
> +++ b/arch/um/include/shared/os.h
> @@ -168,6 +168,7 @@ extern unsigned os_major(unsigned long long dev);
> extern unsigned os_minor(unsigned long long dev);
> extern unsigned long long os_makedev(unsigned major, unsigned minor);
> extern int os_falloc_punch(int fd, unsigned long long offset, int count);
> +extern int os_falloc_zeroes(int fd, unsigned long long offset, int count);
> extern int os_eventfd(unsigned int initval, int flags);
> extern int os_sendmsg_fds(int fd, const void *buf, unsigned int len,
> const int *fds, unsigned int fds_num);
> diff --git a/arch/um/os-Linux/file.c b/arch/um/os-Linux/file.c
> index e4421dbc4c36..fc4450db59bd 100644
> --- a/arch/um/os-Linux/file.c
> +++ b/arch/um/os-Linux/file.c
> @@ -625,6 +625,15 @@ int os_falloc_punch(int fd, unsigned long long offset, int len)
> return n;
> }
>
> +int os_falloc_zeroes(int fd, unsigned long long offset, int len)
> +{
> + int n = fallocate(fd, FALLOC_FL_ZERO_RANGE|FALLOC_FL_KEEP_SIZE, offset, len);
> +
> + if (n < 0)
> + return -errno;
> + return n;
> +}
> +
> int os_eventfd(unsigned int initval, int flags)
> {
> int fd = eventfd(initval, flags);
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2022-01-25 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 17:14 [PATCH] um: Fix WRITE_ZEROES in the UBD Driver Frédéric Danis
2022-01-25 17:56 ` Anton Ivanov [this message]
2022-01-25 18:50 ` Frédéric Danis
2022-01-26 9:47 ` Anton Ivanov
2022-01-26 10:02 ` Frédéric Danis
2022-01-26 10:35 ` Anton Ivanov
2022-01-26 9:47 ` Anton Ivanov
2022-02-16 10:00 ` Frédéric Danis
2022-02-16 17:31 ` Anton Ivanov
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=8de3a6c3-b2fd-648e-ac5f-a27da2d326db@cambridgegreys.com \
--to=anton.ivanov@cambridgegreys.com \
--cc=frederic.danis@collabora.com \
--cc=linux-um@lists.infradead.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