From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Christian Brauner <brauner@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
sunjunchao2870@gmail.com,
Linux Filesystem Development List <linux-fsdevel@vger.kernel.org>,
Christian Brauner <christian@brauner.io>
Subject: Re: [REGRESSION] generic/564 is failing in fs-next
Date: Thu, 24 Oct 2024 09:06:11 +1100 [thread overview]
Message-ID: <20241024090611.0cff2423@canb.auug.org.au> (raw)
In-Reply-To: <20241023194253.GH3204734@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hi Ted,
On Wed, 23 Oct 2024 15:42:53 -0400 "Theodore Ts'o" <tytso@mit.edu> wrote:
>
> 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!!
I have reverted that commit from the fs-next and linux-next trees for
today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-10-23 22:06 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
2024-10-23 22:06 ` Stephen Rothwell [this message]
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=20241024090611.0cff2423@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brauner@kernel.org \
--cc=christian@brauner.io \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sunjunchao2870@gmail.com \
--cc=tytso@mit.edu \
/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