mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Quota, fsnotify, and ext2 changes for 4.10-rc1
Date: Mon, 19 Dec 2016 14:18:32 +0100	[thread overview]
Message-ID: <20161219131832.GA24199@quack2.suse.cz> (raw)
In-Reply-To: <20161219093442.GD17598@quack2.suse.cz>

Hello Linus,

On Mon 19-12-16 10:34:42, Jan Kara wrote:
>   could you please pull from
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus
> 
> to get changes to locking of some quota operations from dedicated quota mutex
> to s_umount semaphore, a fsnotify fix and a simple ext2 fix.
> 
> Top of the tree is 5716863e0f82. The full shortlog is:

Just after sending this pull request I've received a report from 0-day
testing that a warning in dquot_disable() hits on remount. It is just a
cosmetic thing but still I'd prefer to have this fixed and not have to deal
with reports of this warning. So I have pushed out one additional commit
to for_linus branch:

2700e6067c72 "quota: Fix bogus warning in dquot_disable()"

Sorry for the noise. I'm now going to dig into why my personal testing
didn't actually spot this earlier...

								Honza
> 
> Darrick J. Wong (1):
>       ext2: reject inodes with negative size
> 
> Jan Kara (8):
>       fs: Provide function to get superblock with exclusive s_umount
>       quota: Hold s_umount in exclusive mode when enabling / disabling quotas
>       quota: Use s_umount protection for quota operations
>       ocfs2: Protect periodic quota syncing with s_umount semaphore
>       quota: Remove dqonoff_mutex from dquot_scan_active()
>       ocfs2: Use s_umount for quota recovery protection
>       quota: Remove dqonoff_mutex
>       fsnotify: Fix possible use-after-free in inode iteration on umount
> 
> The diffstat is
> 
>  fs/ext2/inode.c         |   4 ++
>  fs/notify/inode_mark.c  |  45 ++++------------
>  fs/ocfs2/quota_global.c |  10 +++-
>  fs/ocfs2/quota_local.c  |  11 ++--
>  fs/ocfs2/super.c        |   1 -
>  fs/quota/dquot.c        | 134 +++++++++++++++++-------------------------------
>  fs/quota/quota.c        |  22 +++++---
>  fs/super.c              |  81 +++++++++++++++++++++--------
>  include/linux/fs.h      |   2 +
>  include/linux/quota.h   |   1 -
>  10 files changed, 151 insertions(+), 160 deletions(-)
> 
> 							Thanks
> 								Honza
> 
> -- 
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2016-12-19 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19  9:34 Jan Kara
2016-12-19 13:18 ` Jan Kara [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=20161219131832.GA24199@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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

Powered by JetHome