public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org,  Christoph Hellwig <hch@lst.de>,
	Jens Axboe <axboe@kernel.dk>,
	 Alexander Viro <viro@zeniv.linux.org.uk>,
	Dave Chinner <david@fromorbit.com>,
	io-uring@vger.kernel.org,  Aishwarya TCV <Aishwarya.TCV@arm.com>
Subject: Re: [PATCH v2] fs: claw back a few FMODE_* bits
Date: Fri, 5 Apr 2024 12:27:41 +0200	[thread overview]
Message-ID: <20240405-vorhof-kolossal-c31693e3fdbe@brauner> (raw)
In-Reply-To: <6fb750e5-650e-42dd-8786-3bf0b2199178@sirena.org.uk>

On Thu, Apr 04, 2024 at 12:43:30PM +0100, Mark Brown wrote:
> On Thu, Apr 04, 2024 at 11:12:15AM +0200, Jan Kara wrote:
> > On Wed 03-04-24 22:12:45, Mark Brown wrote:
> 
> > > For the past couple of days several LTP tests (open_by_handle_at0[12]
> > > and name_to_handle_at01) have been failing on all the arm64 platforms
> > > we're running these tests on.  I ran a bisect which came back to this
> 
> > Do you have some LTP logs / kernel logs available for the failing runs?
> 
> Actually it looks like the issue went away with today's -next, but FWIW
> the logging for the open_by_handle_at0[12] failures was:

The bug was with:

fs: Annotate struct file_handle with __counted_by() and use struct_size()

and was reported and fixed in the thread around:

https://lore.kernel.org/r/20240403110316.qtmypq2rtpueloga@quack3

so this is really unrelated.

  reply	other threads:[~2024-04-05 10:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 12:27 [PATCH v2] fs: claw back a few FMODE_* bits Christian Brauner
2024-03-28 13:08 ` Christoph Hellwig
2024-04-02 10:51 ` Jan Kara
2024-04-02 12:59 ` Jens Axboe
2024-04-03 21:12 ` Mark Brown
2024-04-04  9:12   ` Jan Kara
2024-04-04 11:43     ` Mark Brown
2024-04-05 10:27       ` Christian Brauner [this message]
2024-04-05 11:12         ` Mark Brown
2024-04-04  0:18 ` Al Viro
2024-04-05 10:06   ` Christian Brauner
2024-04-06  6:10 ` Al Viro
2024-04-06  6:16   ` Al Viro
2024-04-09  9:12     ` 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=20240405-vorhof-kolossal-c31693e3fdbe@brauner \
    --to=brauner@kernel.org \
    --cc=Aishwarya.TCV@arm.com \
    --cc=axboe@kernel.dk \
    --cc=broonie@kernel.org \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=io-uring@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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