Re: [GIT PULL] GFS2 changes for 5.9

2020-08-10 Thread pr-tracker-bot 
The pull request you sent on Mon, 10 Aug 2020 20:36:34 +0200:

> git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git 
> tags/gfs2-for-5.9

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8c2618a6d0f7b08e2b41575a87cf568745c8860e

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

[GIT PULL] GFS2 changes for 5.9

2020-08-10 Thread Andreas Gruenbacher 
Hi Linus,

please consider pulling the following gfs2 changes for 5.9.

Thanks a lot,
Andreas

The following changes since commit 11ba468877bb23f28956a35e896356252d63c983:

  Linux 5.8-rc5 (2020-07-12 16:34:50 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git 
tags/gfs2-for-5.9

for you to fetch changes up to e28c02b94f9e039beeb5c75198caf6e17b66c520:

  gfs2: When gfs2_dirty_inode gets a glock error, dump the glock (2020-08-07 
17:26:24 +0200)


Changes in gfs2:

- Make sure transactions won't be started recursively in gfs2_block_zero_range.
  (Bug introduced in 5.4 when switching to iomap_zero_range.)
- Fix a glock holder refcount leak introduced in the iopen glock locking
  scheme rework merged in 5.8.
- A few other small improvements (debugging, stack usage, comment fixes).


Andreas Gruenbacher (3):
  gfs2: Pass glock holder to gfs2_file_direct_{read,write}
  gfs2: Fix refcount leak in gfs2_glock_poke
  fs: Fix typo in comment

Bob Peterson (5):
  gfs2: Add some flags missing from glock output
  gfs2: Fix inaccurate comment
  gfs2: print details on transactions that aren't properly ended
  gfs2: Never call gfs2_block_zero_range with an open transaction
  gfs2: When gfs2_dirty_inode gets a glock error, dump the glock

 fs/gfs2/bmap.c | 69 ++
 fs/gfs2/file.c | 31 
 fs/gfs2/glock.c| 10 +++-
 fs/gfs2/log.c  |  2 +-
 fs/gfs2/super.c|  1 +
 fs/gfs2/trans.c| 29 +--
 include/linux/fs.h |  2 +-
 7 files changed, 82 insertions(+), 62 deletions(-)