mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Miao Xie <miaoxie@huawei.com>, Chao Yu <yuchao0@huawei.com>,
	Fang Wei <fangwei1@huawei.com>,
	Li Guifu <bluce.liguifu@huawei.com>,
	Gao Xiang <hsiangkao@redhat.com>
Subject: [GIT PULL] erofs fixes for 5.9-rc1
Date: Thu, 6 Aug 2020 11:20:17 +0800	[thread overview]
Message-ID: <20200806032017.GA4442@xiangao.remote.csb> (raw)

Hi Linus,

Could you consider this pull request for 5.9-rc1?

This cycle mainly addresses an issue out of some extended inode with
designated location, which can hardly be generated by current mkfs but
needs to handle at runtime anyway. The others are quite trivial ones.

All commits have been tested and have been in linux-next as well.
This merges cleanly with master.

Thanks,
Gao Xiang

The following changes since commit 92ed301919932f777713b9172e525674157e983d:

  Linux 5.8-rc7 (2020-07-26 14:14:06 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-5.9-rc1

for you to fetch changes up to 0e62ea33ac12ebde876b67eca113630805191a66:

  erofs: remove WQ_CPU_INTENSIVE flag from unbound wq's (2020-08-03 21:04:46 +0800)

----------------------------------------------------------------
Changes since last update:

 - use HTTPS links instead of insecure HTTP ones;

 - fix crossing page boundary on specific extended inodes;

 - remove useless WQ_CPU_INTENSIVE flag for unbound wq;

 - minor cleanup.

----------------------------------------------------------------
Alexander A. Klimov (1):
      erofs: Replace HTTP links with HTTPS ones

Gao Xiang (3):
      erofs: fix extended inode could cross boundary
      erofs: fold in used-once helper erofs_workgroup_unfreeze_final()
      erofs: remove WQ_CPU_INTENSIVE flag from unbound wq's

 fs/erofs/compress.h     |   2 +-
 fs/erofs/data.c         |   2 +-
 fs/erofs/decompressor.c |   2 +-
 fs/erofs/dir.c          |   2 +-
 fs/erofs/erofs_fs.h     |   2 +-
 fs/erofs/inode.c        | 123 +++++++++++++++++++++++++++++++-----------------
 fs/erofs/internal.h     |   2 +-
 fs/erofs/namei.c        |   2 +-
 fs/erofs/super.c        |   2 +-
 fs/erofs/utils.c        |  16 ++-----
 fs/erofs/xattr.c        |   2 +-
 fs/erofs/xattr.h        |   2 +-
 fs/erofs/zdata.c        |   6 +--
 fs/erofs/zdata.h        |   2 +-
 fs/erofs/zmap.c         |   2 +-
 fs/erofs/zpvec.h        |   2 +-
 16 files changed, 100 insertions(+), 71 deletions(-)


             reply	other threads:[~2020-08-06  3:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06  3:20 Gao Xiang [this message]
2020-08-07  2:39 ` pr-tracker-bot

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=20200806032017.GA4442@xiangao.remote.csb \
    --to=hsiangkao@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bluce.liguifu@huawei.com \
    --cc=fangwei1@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yuchao0@huawei.com \
    /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

all inboxes | Powered by JetHome®