linux-kernel - Re: [GIT PULL] logfs: some important bug fixes

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>] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 26 Aug 2012 16:56:40 +0530
From:	Prasad Joshi <prasadjoshi.linux@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org,
	Jörn Engel <joern@...fs.org>
Subject: Re: [GIT PULL] logfs: some important bug fixes

Hello Linus,

Could you please pull the following changes since commit
dd775ae2549217d3ae09363e3edb305d0fa19928:

  Linux 3.4-rc1 (2012-03-31 16:24:09 -0700)

are available in the git repository at:
  git://github.com/prasad-joshi/logfs_upstream.git master

Prasad Joshi (5):
      logfs: destroy the reserved inodes while unmounting
      logfs: initialize the number of iovecs in bio
      logfs: create a pagecache page if it is not present
      logfs: maintain the ordering of meta-inode destruction
      logfs: query block device for number of pages to send with bio

 fs/logfs/dev_bdev.c  |   15 +++++++--------
 fs/logfs/inode.c     |   18 +++++++++++++++++-
 fs/logfs/journal.c   |    2 +-
 fs/logfs/readwrite.c |    1 -
 fs/logfs/segment.c   |    2 +-
 5 files changed, 26 insertions(+), 12 deletions(-)

Please note that the signed tag (for-linus) is applied and the same is
pushed. The repository is also added in the 'linux-next' and there no
conflicts in the 'linux-next: Tree for Aug 24'.

Thanks and Warm Regards,
Prasad
--
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/