linux-kernel - [GIT PULL] fuse bugfixes for 3.10-rc5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20130604080125.GD1842@tucsk.piliscsaba.szeredi.hu>
Date:	Tue, 4 Jun 2013 10:01:25 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux-Fsdevel <linux-fsdevel@...r.kernel.org>,
	Maxim Patlasov <mpatlasov@...allels.com>
Subject: [GIT PULL] fuse bugfixes for 3.10-rc5

Hi Linus,

Please pull the following bugfixes for fuse:

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus

One patch fixes an Oops introduced in 3.9 with the readdirplus feature.  The
rest are fixes for async-dio in 3.10.

Thanks,
Miklos

---
Brian Foster (4):
      fuse: allocate for_background dio requests based on io->async state
      fuse: truncate pagecache range on hole punch
      fuse: update inode size and invalidate attributes on fallocate
      fuse: return -EIOCBQUEUED from fuse_direct_IO() for all async requests

Maxim Patlasov (1):
      fuse: fix alignment in short read optimization for async_dio

Miklos Szeredi (1):
      fuse: fix readdirplus Oops in fuse_dentry_revalidate

---
 fs/fuse/dir.c   |   12 +++++++++---
 fs/fuse/file.c  |   58 ++++++++++++++++++++++++++++++++++++++++++++++---------
 fs/fuse/inode.c |    7 ++++---
 3 files changed, 62 insertions(+), 15 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/