All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Evgeniy Dushistov <dushistov@mail.ru>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] remove most callers of write_one_page v3
Date: Thu, 19 Jan 2023 06:28:21 +0100	[thread overview]
Message-ID: <20230119052821.GA16631@lst.de> (raw)
In-Reply-To: <Y8hlrJJZ2uJbZSCv@ZenIV>

On Wed, Jan 18, 2023 at 09:33:32PM +0000, Al Viro wrote:
> BTW, do you have the check for minix_delete_entry() failure when called
> from minix_rename() anywhere in your tree?  I don't see that in this
> series; I'm adding the trivial fix, hopefully that won't end up
> creating conflicts...

Just add it in top of the series, I didn't touch anything that I did
not send out.

_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
	Joseph Qi <joseph.qi@linux.alibaba.com>,
	Evgeniy Dushistov <dushistov@mail.ru>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	ocfs2-devel@oss.oracle.com, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: remove most callers of write_one_page v3
Date: Thu, 19 Jan 2023 06:28:21 +0100	[thread overview]
Message-ID: <20230119052821.GA16631@lst.de> (raw)
In-Reply-To: <Y8hlrJJZ2uJbZSCv@ZenIV>

On Wed, Jan 18, 2023 at 09:33:32PM +0000, Al Viro wrote:
> BTW, do you have the check for minix_delete_entry() failure when called
> from minix_rename() anywhere in your tree?  I don't see that in this
> series; I'm adding the trivial fix, hopefully that won't end up
> creating conflicts...

Just add it in top of the series, I didn't touch anything that I did
not send out.

  reply	other threads:[~2023-01-19  5:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 17:30 [Ocfs2-devel] remove most callers of write_one_page v3 Christoph Hellwig via Ocfs2-devel
2023-01-18 17:30 ` Christoph Hellwig
2023-01-18 17:30 ` [Ocfs2-devel] [PATCH 1/7] minix: move releasing pages into unlink and rename Christoph Hellwig via Ocfs2-devel
2023-01-18 17:30   ` Christoph Hellwig
2023-01-18 17:30 ` [Ocfs2-devel] [PATCH 2/7] minix: fix error handling in minix_delete_entry Christoph Hellwig via Ocfs2-devel
2023-01-18 17:30   ` Christoph Hellwig
2023-01-18 17:30 ` [Ocfs2-devel] [PATCH 3/7] minix: fix error handling in minix_set_link Christoph Hellwig via Ocfs2-devel
2023-01-18 17:30   ` Christoph Hellwig
2023-01-18 17:30 ` [Ocfs2-devel] [PATCH 4/7] minix: don't flush page immediately for DIRSYNC directories Christoph Hellwig via Ocfs2-devel
2023-01-18 17:30   ` Christoph Hellwig
2023-01-18 17:30 ` [Ocfs2-devel] [PATCH 5/7] sysv: " Christoph Hellwig via Ocfs2-devel
2023-01-18 17:30   ` Christoph Hellwig
2023-01-18 17:30 ` [Ocfs2-devel] [PATCH 6/7] ufs: " Christoph Hellwig via Ocfs2-devel
2023-01-18 17:30   ` Christoph Hellwig
2023-01-18 17:30 ` [Ocfs2-devel] [PATCH 7/7] ocfs2: don't use write_one_page in ocfs2_duplicate_clusters_by_page Christoph Hellwig via Ocfs2-devel
2023-01-18 17:30   ` Christoph Hellwig
2023-01-18 21:09 ` [Ocfs2-devel] remove most callers of write_one_page v3 Andrew Morton via Ocfs2-devel
2023-01-18 21:09   ` Andrew Morton
2023-01-18 21:23 ` [Ocfs2-devel] " Al Viro via Ocfs2-devel
2023-01-18 21:23   ` Al Viro
2023-01-18 21:33   ` [Ocfs2-devel] " Al Viro via Ocfs2-devel
2023-01-18 21:33     ` Al Viro
2023-01-19  5:28     ` Christoph Hellwig via Ocfs2-devel [this message]
2023-01-19  5:28       ` Christoph Hellwig

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=20230119052821.GA16631@lst.de \
    --to=ocfs2-devel@oss.oracle.com \
    --cc=dushistov@mail.ru \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.