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: LKML <linux-kernel@vger.kernel.org>, linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] Notification, writeback, udf, quota fixes for 3.14-rc5
Date: Wed, 26 Feb 2014 17:55:40 +0100	[thread overview]
Message-ID: <20140226165540.GA28856@quack.suse.cz> (raw)

  Hello Linus,

  could you please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus

to get several fixes. Notification patches are (with one exception) a fallout
of my fsnotify rework which went into -rc1 (I've extented LTP to cover these
cornercases to avoid similar breakage in future). UDF patch is a nasty data
corruption Al has recently reported, revert of writeback patch is due to
possibility of violating sync(2) guarantees, and quota bug can lead to
corruption of quota files in ocfs2.  Top of the tree is ff57cd5863cf. The full
shortlog is:

Jan Kara (7):
      inotify: Fix reporting of cookies for inotify events
      udf: Fix data corruption on file type conversion
      quota: Fix race between dqput() and dquot_scan_active()
      Revert "writeback: do not sync data dirtied after sync start"
      fsnotify: Fix detection whether overflow event is queued
      fanotify: Handle overflow in case of permission events
      fsnotify: Allocate overflow events with proper type

The diffstat is

 fs/fs-writeback.c                    | 33 +++++++++++----------------------
 fs/notify/dnotify/dnotify.c          |  2 +-
 fs/notify/fanotify/fanotify.c        |  8 +++++---
 fs/notify/fanotify/fanotify_user.c   | 13 +++++++++++++
 fs/notify/fsnotify.c                 |  2 +-
 fs/notify/group.c                    |  8 +++++++-
 fs/notify/inotify/inotify.h          |  2 +-
 fs/notify/inotify/inotify_fsnotify.c |  3 ++-
 fs/notify/inotify/inotify_user.c     | 14 +++++++++++++-
 fs/notify/notification.c             | 20 +++++++++++++++-----
 fs/quota/dquot.c                     | 14 +++++++++++---
 fs/sync.c                            | 15 ++++++---------
 fs/udf/file.c                        | 14 ++++++++++++--
 fs/udf/inode.c                       |  1 +
 fs/xfs/xfs_super.c                   |  2 +-
 include/linux/fsnotify_backend.h     |  4 ++--
 include/linux/writeback.h            |  2 +-
 include/trace/events/writeback.h     |  6 +++---
 kernel/audit_tree.c                  |  2 +-
 kernel/audit_watch.c                 |  2 +-
 20 files changed, 108 insertions(+), 59 deletions(-)

							Thanks
								Honza

-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

                 reply	other threads:[~2014-02-26 16:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140226165540.GA28856@quack.suse.cz \
    --to=jack@suse.cz \
    --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

all inboxes | Powered by JetHome®