From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
David Sterba <dsterba@suse.com>, Jan Kara <jack@suse.cz>,
Mike Marshall <hubcap@omnibond.com>,
Martin Brandenburg <martin@omnibond.com>,
Carlos Maiolino <cem@kernel.org>, Stefan Roesch <shr@fb.com>,
Jeff Layton <jlayton@kernel.org>,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, gfs2@lists.linux.dev,
io-uring@vger.kernel.org, devel@lists.orangefs.org,
linux-unionfs@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-xfs@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: re-enable IOCB_NOWAIT writes to files v4
Date: Mon, 12 Jan 2026 14:22:11 +0100 [thread overview]
Message-ID: <20260112-canceln-skript-95f066b9fcc1@brauner> (raw)
In-Reply-To: <20260112100558.GA7670@lst.de>
On Mon, Jan 12, 2026 at 11:05:58AM +0100, Christoph Hellwig wrote:
> On Mon, Jan 12, 2026 at 11:04:17AM +0100, Christian Brauner wrote:
> > On Wed, Jan 07, 2026 at 08:32:47AM +0100, Christoph Hellwig wrote:
> > > On Tue, Jan 06, 2026 at 10:43:49PM +0100, Christian Brauner wrote:
> > > > > Umm, as in my self reply just before heading out for vacation, Julia
> > > > > found issues in it using static type checking tools. I have a new
> > > > > version that fixes that and sorts out the S_* mess. So please drop
> > > > > it again for now, I'll resend the fixed version ASAP.
> > > >
> > > > It has never been pushed nor applied as I saw your mail right before all
> > > > of that.
> > >
> > > Thanks. But maybe you can fix up the applied messages to be more
> > > specific? We had various issues in the past with them, where they
> > > were sent, but things did not end up in the tree for various reasons.
> >
> > What are you thinking of exactly?
>
> Only send out the applied message when something is actually pushed
> to the public tree?
When that happens it usually means that it's still waiting on tests.
I can pay more attention to this but don't expect it to be perfect in
all cases.
prev parent reply other threads:[~2026-01-12 13:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 0:37 re-enable IOCB_NOWAIT writes to files v4 Christoph Hellwig
2025-12-23 0:37 ` [PATCH 01/11] fs: remove inode_update_time Christoph Hellwig
2025-12-23 0:37 ` [PATCH 02/11] fs: allow error returns from generic_update_time Christoph Hellwig
2025-12-23 0:37 ` [PATCH 03/11] fs: exit early in generic_update_time when there is no work Christoph Hellwig
2025-12-23 5:33 ` Chaitanya Kulkarni
2025-12-23 0:37 ` [PATCH 04/11] fs: delay the actual timestamp updates in inode_update_timestamps Christoph Hellwig
2025-12-23 5:35 ` Chaitanya Kulkarni
2025-12-23 0:37 ` [PATCH 05/11] fs: return I_DIRTY_* and allow error returns from inode_update_timestamps Christoph Hellwig
2025-12-23 5:36 ` Chaitanya Kulkarni
2025-12-29 7:27 ` kernel test robot
2025-12-23 0:37 ` [PATCH 06/11] fs: factor out a sync_lazytime helper Christoph Hellwig
2025-12-23 5:36 ` Chaitanya Kulkarni
2025-12-23 0:37 ` [PATCH 07/11] fs: add a ->sync_lazytime method Christoph Hellwig
2025-12-23 5:37 ` Chaitanya Kulkarni
2025-12-23 0:37 ` [PATCH 08/11] fs: add support for non-blocking timestamp updates Christoph Hellwig
2025-12-23 5:38 ` Chaitanya Kulkarni
2025-12-23 0:37 ` [PATCH 09/11] fat: enable " Christoph Hellwig
2025-12-23 0:37 ` [PATCH 10/11] xfs: implement ->sync_lazytime Christoph Hellwig
2025-12-23 0:37 ` [PATCH 11/11] xfs: enable non-blocking timestamp updates Christoph Hellwig
2025-12-23 5:39 ` Chaitanya Kulkarni
2025-12-23 22:53 ` re-enable IOCB_NOWAIT writes to files v4 Christoph Hellwig
2025-12-24 13:11 ` Christian Brauner
2026-01-06 6:24 ` Christoph Hellwig
2026-01-06 21:43 ` Christian Brauner
2026-01-07 7:32 ` Christoph Hellwig
2026-01-12 10:04 ` Christian Brauner
2026-01-12 10:05 ` Christoph Hellwig
2026-01-12 13:22 ` Christian Brauner [this message]
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=20260112-canceln-skript-95f066b9fcc1@brauner \
--to=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=devel@lists.orangefs.org \
--cc=dsterba@suse.com \
--cc=gfs2@lists.linux.dev \
--cc=hch@lst.de \
--cc=hubcap@omnibond.com \
--cc=io-uring@vger.kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=martin@omnibond.com \
--cc=shr@fb.com \
--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