public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it, linuxtestproject.agent@gmail.com
Subject: Re: [LTP] lib: Treat kernel ntfs3 as a separate FS
Date: Mon, 13 Apr 2026 23:24:40 +0200	[thread overview]
Message-ID: <20260413212440.GB164377@pevik> (raw)
In-Reply-To: <adz_e3PJmL9RPMt7@yuki.lan>

Hi Cyril,

> Hi!
> > > lib: Treat kernel ntfs3 as a separate FS

Reviewed-by: Petr Vorel <pvorel@suse.cz>

Great idea, thanks!

> > > Meanwhile this even caused failures, which is how this issue finaly
> > > surfaced with a fuse based NTFS not being skipped properly because the
> > > test library got confused with having both kernel and fuse NTFS
> > > available.

> > Two typos: "finaly" -> "finally", "callled" -> "called" (a few lines
> > below).

> I will fix these before commiting.

> > Since this fixes a real failure, please consider adding a Fixes: tag
> > pointing to the LTP commit that introduced the broken ntfs handling. If
> > the issue predates any single identifiable commit, dropping the tag is
> > fine — just clarify in the reply.

> However this one is more complex, there isn't a single patch that caused
> the problem, moreover it was triggered only by addition of the ntfs3
> driver into the kernel.

+1.

Trying, if patchwork / b4 takes this tag (link to lore). It'd be great if we had
tooling patchwork.kernel.org + git.kernel.org have so that we would not have to
add it manually.
Link: https://lore.kernel.org/ltp/20260413115129.30239-1-chrubis@suse.cz/

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-04-13 21:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 11:51 [LTP] [PATCH] lib: Treat kernel ntfs3 as a separate FS Cyril Hrubis
2026-04-13 12:22 ` [LTP] " linuxtestproject.agent
2026-04-13 14:36   ` Cyril Hrubis
2026-04-13 21:24     ` Petr Vorel [this message]
2026-04-14  8:58 ` [LTP] [PATCH] " Avinesh Kumar via ltp
2026-04-16 15:43 ` Cyril Hrubis

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=20260413212440.GB164377@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=linuxtestproject.agent@gmail.com \
    --cc=ltp@lists.linux.it \
    /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