public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Horst Birthelmer <horst@birthelmer.de>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: kernel test robot <oliver.sang@intel.com>,
	 Horst Birthelmer <horst@birthelmer.com>,
	lkp@intel.com, Miklos Szeredi <miklos@szeredi.hu>,
	 Bernd Schubert <bernd@bsbernd.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	 Horst Birthelmer <hbirthelmer@ddn.com>,
	ltp@lists.linux.it, oe-lkp@lists.linux.dev,
	 Joanne Koong <joannelkoong@gmail.com>
Subject: Re: Re: [LTP] [PATCH] fuse: when copying a folio delay the mark dirty until the end
Date: Thu, 26 Mar 2026 16:44:02 +0100	[thread overview]
Message-ID: <acVT7mE4MjBfNPOW@fedora> (raw)
In-Reply-To: <acVLK8F8i-eEZwLG@yuki.lan>

On Thu, Mar 26, 2026 at 04:05:15PM +0100, Cyril Hrubis wrote:
> Hi!
> > commit: 47f8dde97f35e32a1003d54e387273bcdf014ddf ("[PATCH] fuse: when copying a folio delay the mark dirty until the end")
> > url: https://github.com/intel-lab-lkp/linux/commits/Horst-Birthelmer/fuse-when-copying-a-folio-delay-the-mark-dirty-until-the-end/20260316-234418
> > patch link: https://lore.kernel.org/all/20260316-mark-dirty-per-folio-v1-1-8dc39c94b7ce@ddn.com/
> > patch subject: [PATCH] fuse: when copying a folio delay the mark dirty until the end
> > 
> > in testcase: ltp
> > version: 
> > with following parameters:
> > 
> > 	disk: 1HDD
> > 	fs: ext4
> > 	test: fs-03
> 
> Looks like the test that has failed was fs_fill that runs several
> threads that attempt to fill the filesystem (until they get ENOSCP) then
> delete the files and try again. And apparently we managed to get EIO
> when file has been closed() by one of the threads after a few minutes of
> the runtime on NTFS mounted over FUSE.
> 
Probably nothing to do with the patch itself, but the patch will never
make it since it contains a wrong assumption.

Thanks for clarifying!

> -- 
> Cyril Hrubis
> chrubis@suse.cz

Horst

      reply	other threads:[~2026-03-26 15:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 15:16 [PATCH] fuse: when copying a folio delay the mark dirty until the end Horst Birthelmer
2026-03-16 17:29 ` Joanne Koong
2026-03-16 20:02   ` Horst Birthelmer
2026-03-16 22:06     ` Joanne Koong
2026-03-18 14:03       ` Horst Birthelmer
2026-03-18 21:19         ` Joanne Koong
2026-03-18 21:52           ` Bernd Schubert
2026-03-19  1:32             ` Joanne Koong
2026-03-19  4:27               ` Darrick J. Wong
2026-03-20 17:24                 ` Joanne Koong
2026-03-19  8:32               ` Horst Birthelmer
2026-03-20 17:18                 ` Joanne Koong
2026-03-26  6:35 ` kernel test robot
2026-03-26 15:05   ` [LTP] " Cyril Hrubis
2026-03-26 15:44     ` Horst Birthelmer [this message]

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=acVT7mE4MjBfNPOW@fedora \
    --to=horst@birthelmer.de \
    --cc=bernd@bsbernd.com \
    --cc=chrubis@suse.cz \
    --cc=hbirthelmer@ddn.com \
    --cc=horst@birthelmer.com \
    --cc=joannelkoong@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=ltp@lists.linux.it \
    --cc=miklos@szeredi.hu \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    /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