Linux filesystem development
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Christian Brauner <brauner@kernel.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	sunjunchao2870@gmail.com,
	Linux Filesystem Development List <linux-fsdevel@vger.kernel.org>,
	Christian Brauner <christian@brauner.io>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [REGRESSION] generic/564 is failing in fs-next
Date: Wed, 23 Oct 2024 15:42:53 -0400	[thread overview]
Message-ID: <20241023194253.GH3204734@mit.edu> (raw)
In-Reply-To: <20241021-anstecken-fortfahren-4dd7b79a5f45@brauner>

On Mon, Oct 21, 2024 at 02:49:54PM +0200, Christian Brauner wrote:
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/fs/read_write.c?h=fs-next&id=0f0f217df68fd72d91d2de6e85a6dd80fa1f5c95
> > 
> > To Mr. Sun: did you see these regressions when you tested this patch?
> 
> So we should drop this patch for now.

My most recent fs-next testing is still showing this failure, and
looking at the most recent fs-next branch, 

    vfs: Fix implicit conversion problem when testing overflow case

still appears to be in the tree.  Can we please get this dropped?
Thanks!!

							- Ted

  parent reply	other threads:[~2024-10-23 19:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 16:28 [REGRESSION] generic/564 is failing in fs-next Theodore Ts'o
2024-10-19 16:16 ` Darrick J. Wong
2024-10-21 12:49   ` Christian Brauner
2024-10-21 18:15     ` Darrick J. Wong
2024-10-23 19:42     ` Theodore Ts'o [this message]
2024-10-23 22:06       ` Stephen Rothwell
2024-10-25 15:18         ` Christian Brauner

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=20241023194253.GH3204734@mit.edu \
    --to=tytso@mit.edu \
    --cc=brauner@kernel.org \
    --cc=christian@brauner.io \
    --cc=djwong@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sunjunchao2870@gmail.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