linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Christoph Hellwig <hch@lst.de>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>, Al Viro <viro@zeniv.linux.org.uk>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mm: require ->set_page_dirty to be explicitly wire up
Date: Fri, 18 Jun 2021 22:23:55 +0300	[thread overview]
Message-ID: <ddafcc0d-8636-46ca-44b7-54392e0d22b4@gmail.com> (raw)
In-Reply-To: <20210614061512.3966143-4-hch@lst.de>

14.06.2021 09:15, Christoph Hellwig пишет:
> Remove the CONFIG_BLOCK default to __set_page_dirty_buffers and just
> wire that method up for the missing instances.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  fs/adfs/inode.c     |  1 +
>  fs/affs/file.c      |  2 ++
>  fs/bfs/file.c       |  1 +
>  fs/block_dev.c      |  1 +
>  fs/exfat/inode.c    |  1 +
>  fs/ext2/inode.c     |  2 ++
>  fs/fat/inode.c      |  1 +
>  fs/gfs2/meta_io.c   |  2 ++
>  fs/hfs/inode.c      |  2 ++
>  fs/hfsplus/inode.c  |  2 ++
>  fs/hpfs/file.c      |  1 +
>  fs/jfs/inode.c      |  1 +
>  fs/minix/inode.c    |  1 +
>  fs/nilfs2/mdt.c     |  1 +
>  fs/ocfs2/aops.c     |  1 +
>  fs/omfs/file.c      |  1 +
>  fs/sysv/itree.c     |  1 +
>  fs/udf/file.c       |  1 +
>  fs/udf/inode.c      |  1 +
>  fs/ufs/inode.c      |  1 +
>  mm/page-writeback.c | 18 ++++--------------
>  21 files changed, 29 insertions(+), 14 deletions(-)

The ecryptfs is now crashing with NULL deference, please fix.

  parent reply	other threads:[~2021-06-18 19:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14  6:15 remove the implicit .set_page_dirty default Christoph Hellwig
2021-06-14  6:15 ` [PATCH 1/3] fs: unexport __set_page_dirty Christoph Hellwig
2021-06-14  6:23   ` Greg Kroah-Hartman
2021-06-14  9:42   ` Jan Kara
2021-06-14 12:32   ` Matthew Wilcox
2021-06-14 15:52     ` Christoph Hellwig
2021-06-14  6:15 ` [PATCH 2/3] fs: move ramfs_aops to libfs Christoph Hellwig
2021-06-14  6:24   ` Greg Kroah-Hartman
2021-06-14  9:45   ` Jan Kara
2021-06-14  6:15 ` [PATCH 3/3] mm: require ->set_page_dirty to be explicitly wire up Christoph Hellwig
2021-06-14  6:24   ` Greg Kroah-Hartman
2021-06-14  9:51   ` Jan Kara
2021-06-14 10:03     ` Christoph Hellwig
2021-06-18 19:23   ` Dmitry Osipenko [this message]
2021-06-21  5:26     ` Christoph Hellwig
2021-06-14 12:23 ` remove the implicit .set_page_dirty default Matthew Wilcox
2021-06-14 15:53   ` Christoph Hellwig
2021-06-14 15:55     ` Christoph Hellwig
2021-06-14 16:17       ` Matthew Wilcox

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=ddafcc0d-8636-46ca-44b7-54392e0d22b4@gmail.com \
    --to=digetx@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).