STEVE KOFFI | 24 May 01:03 2015
Picon

THANKS

Mr. Steve Koffi, From Tema Ghana staff of Standard Chartered Bank
Ghana,I have A business proposal of (US$4,450,000.00), for you from my
Bank which I need your co-operation as my partner to transfer this
Money to your bank account within Five (5) working days. This
transaction is legal without any problem and it is bank to bank
transfer and 100% risk free.
As soon as the four Million four Hundred and Fifty Thousand Dollar
[$4,450.000.00]is transferred to your bank account, you shall take
40%, while I take 60%. If you are interested to work with me reply my
email so I can send you more details. And I can provide any needed
document during the transfer.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Qing Chang | 23 May 02:35 2015
Picon

From: Qing Chang


Good morning linux

http://elemi.ca/come.php?garden=7dkb7h55yvewzubk

changq <at> gmail.com

Sent from my iPhone
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Tejun Heo | 22 May 23:13 2015

[PATCHSET 1/3 v4 block/for-4.2/core] writeback: cgroup writeback support

Hello,

This is v4 of cgroup writeback support patchset.  Changes from the
last take[L] are

* b9ea25152e56 ("page_writeback: clean up mess around
  cancel_dirty_page()") replaced cancel_dirty_page() with
  account_page_cleaned() which pushed clearing the dirty flag to the
  caller; however, changes in this patchset and the following ones
  require synchronization between dirty clearing and stat updates
  which is a lot easier with a helper which does both operations.

  0001-page_writeback-revive-cancel_dirty_page-in-a-restric.patch is
  added to resurrect cancel_dirty_page() in a more restricted form.

* Recent dirtytime changes added wakeup_dirtytime_writeback() which
  needs to be updated to walk through all wb's.
  0042-writeback-make-wakeup_dirtytime_writeback-handle-mul.patch
  added.

* Rebased on top of the current block/for-4.2/core.

blkio cgroup (blkcg) is severely crippled in that it can only control
read and direct write IOs.  blkcg can't tell which cgroup should be
held responsible for a given writeback IO and charges all of them to
the root cgroup - all normal write traffic ends up in the root cgroup.
Although the problem has been identified years ago, mainly because it
interacts with so many subsystems, it hasn't been solved yet.

This patchset finally implements cgroup writeback support so that
(Continue reading)

Daeyong Shin | 22 May 16:27 2015
Picon

Request to join 'Support for atomic IOs

Hello,

I'm Daeyong Shin, a researcher at Korea Electronics Technology Institute.
Your work inspire me and I want to join 'Support for atomic IOs' group.

 The reason I send this mail to you is probably, Chris's mail box is full.

I already send a mail to Chris Mason but it doesn't receive my mail.

 If there is any form to join the group, I'm sorry I didn't find it and
I'll do it right away.

Best regards,
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Daeyong Shin | 22 May 16:21 2015
Picon

Request to join 'Support for atomic IOs

Hello,

I'm Daeyong Shin, a researcher at Korea Electronics Technology Institute.
Your work inspire me and I want to join 'Support for atomic IOs' group.

  The reason I send this mail to you is probably, Chris's mail box is full.

I already send a mail to Chris Mason but it doesn't receive my mail.

  If there is any form to join the group, I'm sorry I didn't find it and
I'll do it right away.

Best regards,

Daeyong Shin
Assistant Researcher
Medical IT Convergence Research Center
Convergence Industries R&D Division
Korea Electronics Technology Institute
25, Saenari-ro, Bundang-gu, Seongnam-si, Gyeonggi-do, 463-816 Korea
Phone: +82-31-7897-000
Email: daeyong <at> keti.re.kr

---
이 이메일은 Avast 안티바이러스 소프트웨어로 바이러스 검사를 완료했습니다.
http://www.avast.com

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
(Continue reading)

Jan Kara | 21 May 16:05 2015
Picon

[PATCH 0/5 v4] fs: Fixes for removing xid bits and security labels

  Hello,

  This is the fourth version of my patches to fix handling of s[ug]id bits and
capabilities xattrs in VFS. There are a few issues I found:

1) MS_NOSEC handling is broken - we set it after each file_remove_suid() call.
   However we needn't have removed suid bit simply because we have
   CAP_SYS_FSID and further writes to the file from processes without this
   capability still need to clear the suid bit.
2) file_remove_suid() is a misnomer since it also handles removing of
   file capabilities. It is even more confusing because should_remove_suid()
   doesn't return whether file_remove_suid() is needed or not.
3) On truncate we do clear suid bits but not file capabilities.
4) ocfs2 doesn't clear capability xattrs - hard to fix, I left it alone for
   now.
5) XFS didn't provide proper exclusion for clearing mode bits.

  This series aims at fixing above issues. Al, can you please merge the
patches? Thanks!

  Changes since v3:
* Updated changelogs and some comments to speak about capabilities and not
  security labels.

  Changes since v2:
* Rebased on top of current Linus' tree
* Improved patch 1 to use inode_has_no_xattr() as Linus suggested

  Changes since v1:
* Removed bogus patch changing inode_set_flags()
(Continue reading)

Ivan Delalande | 15 May 20:58 2015

Warning: empty root dentry name after lazy mount removal

Hi,

Since commit 8ed936b "vfs: Lazily remove mounts on unlinked files and
directories.", I’m seeing a new warning from prepend_path() at
fs/dcache.c:2937 saying:

	Root dentry has weird name <>

Our particular occurrence happens because we are using an older version
of iproute (< v3.10, commit bcb9d40, but this also works with the master
and just reverting that commit), and the following scenario:

	term1# ip netns add foo
	term1# ip netns exec foo sh
	term1# ls -l /proc/self/fd/4
	lr-x------ 1 root root 64 May 15 11:02 /proc/self/fd/4 -> /var/run/netns/foo
	term2# ip netns del foo
	term1# ls -l /proc/self/fd/4
	[dmesg] WARNING: [...]
	[dmesg] Root dentry has weird name <>
	lr-x------ 1 root root 64 May 15 11:04 /proc/self/fd/4 -> /

Relevant moutinfo chunks before the `ip netns del`:

	29 0 8:2 / / rw,relatime - ext4 /dev/sda2 rw,data=ordered
	82 29 0:3 / /var/run/netns/foo rw,nosuid,nodev,noexec,relatime - proc proc rw

What I could observe is that after the namespace deletion, that mount 82
get isolated (mnt->parent = mnt), and so prepend_path considers it as
the global root. But the name of that dentry has d_name.len == 0, which
(Continue reading)

Josef Bacik | 18 May 21:50 2015

[PATCH 1/2] fstests: add dm-log-writes test and supporting code

This patch adds the supporting code for using the dm-log-writes target.  The
bash stuff is similar to the dmflakey code, it just gives us functions to build
and tear down a dm-log-writes target.  We add a new LOGWRITES_DEV variable to
take in the device we will use as the log and add checks for that.

I've rigged up fsx to have an integrity check mode.  Basically it works like it
normally works, but when it fsync()'s it marks the log with a unique mark and
dumps it's buffer to a file with the mark in the filename.  I did this with a
system() call simply because it was the fastest.  I can link the device-mapper
libraries and do it programatically if that would be preferred, but this works
pretty well.

The test itself just runs 200 ops and exits, then finds all of the good buffers
in the directory we provided and replays up to the mark given, mounts the file
system and compares the md5sum, unmounts and fsck's to check for metadata
integrity.  dm-log-writes will pretend to do discard and the replay tool will
replay it properly depending on the underlying device, either by writing 0's or
actually calling the discard ioctl, so I've enabled discard in the test for
maximum fun.

This test relies on the supporting userspace code I've written for
dm-logs-writes.  It can be found here

https://github.com/josefbacik/log-writes.git

Thanks,

Signed-off-by: Josef Bacik <jbacik <at> fb.com>
---
 README                |   2 +
(Continue reading)

Miklos Szeredi | 18 May 17:13 2015
Picon

fuse scalability part 1

This part splits out an "input queue" and a "processing queue" from the
monolithic "fuse connection", each of those having their own spinlock.

The end of the patchset adds the ability to "clone" a fuse connection.  This
means, that instead of having to read/write requests/answers on a single fuse
device fd, the fuse daemon can have multiple distinct file descriptors open.
Each of those can be used to receive requests and send answers, currently the
only constraint is that a request must be answered on the same fd as it was read
from.

This can be extended further to allow binding a device clone to a specific CPU
or NUMA node.

Patchset is available here:

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

Libfuse patches adding support for "clone_fd" option:

  git://git.code.sf.net/p/fuse/fuse clone_fd

Thanks,
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Bob Copeland | 18 May 13:34 2015

[PATCH 0/4] OMFS fixes

Hi all, this patchset includes fixes for omfs, three by me and
one by Sasha Levin that hasn't been picked up elsewhere.  1 and 3
fix quite nasty crashes.  Andrew, you have taken omfs patches
through your tree before, mind taking these?

Bob Copeland (3):
  omfs: set error return when d_make_root() fails
  omfs: fix sign confusion for bitmap loop counter
  omfs: fix potential integer overflow in allocator

Sasha Levin (1):
  fs, omfs: add NULL terminator in the end up the token list

 fs/omfs/bitmap.c |  2 +-
 fs/omfs/inode.c  | 10 +++++++---
 2 files changed, 8 insertions(+), 4 deletions(-)

--

-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Mark Tomlinson | 18 May 06:54 2015
Picon

[PATCH 0/1] JFFS2: Less locking when reading directory entries

I have posted this before, but have extended the patch into a few more
functions. The intent of the code is as before -- to improve JFFS2 lookups
by not locking i_mutex for long periods when files are not in cache. For
our embedded environment, we see a *five second* improvement in boot time.

This patch is an attempt to improve the speed of JFFS2 at startup. Our
particular problem is that we have a 30MB file on NOR flash which takes
about five seconds to read and test the data CRCs. During this time access
to other files in the same directory is blocked, due to
parent->d_inode->i_mutex being locked.

This patch solves this problem by adding a 'pre-lookup' call down to JFFS2,
which can be called without this mutex held. When the actual lookup is
performed, the results are in JFFS2's cache, and the dentry can be filled
in quickly.

However, given that I do not have experience at Linux filesystem code,
I can't be sure that this is a correct solution, or that there isn't a
better way of achieving what I'm trying to do. I feel there must be a way
to do this without creating a new VFS function call.

I suspect other filesystems could benefit from this too, as a lot of them
call the same d_splice_alias() function to fill in the dentry. JFFS2
already seems to have all the lower-level locks that are needed for this to
work; I don't know if that's true in other filesystems which could be
relying on the directory's i_mutex being locked. Because JFFS2 needs to
walk the entire file, there are big gains to be made here; other filesystems
may gain little to nothing.

I'm not expecting that this patch will get applied as-is, but please let me
(Continue reading)


Gmane