From: Mark Brown <[email protected]>
To: Christian Brauner <[email protected]>
Cc: Jan Kara <[email protected]>,
[email protected], Christoph Hellwig <[email protected]>,
Jens Axboe <[email protected]>,
Alexander Viro <[email protected]>,
Dave Chinner <[email protected]>,
[email protected], Aishwarya TCV <[email protected]>
Subject: Re: [PATCH v2] fs: claw back a few FMODE_* bits
Date: Fri, 5 Apr 2024 12:12:50 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <20240405-vorhof-kolossal-c31693e3fdbe@brauner>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
On Fri, Apr 05, 2024 at 12:27:41PM +0200, Christian Brauner wrote:
> On Thu, Apr 04, 2024 at 12:43:30PM +0100, Mark Brown wrote:
> > 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.
Ah, good - I did actually get to that one on my original bisect but
reran the final section of the bisect since it looked like a false
positive and wanted to confirm. Not sure why it glitched on the second
run.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-04-05 11:12 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
2024-04-05 11:12 ` Mark Brown [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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