<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/staging/lustre/include, branch master</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=master</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2018-06-05T17:22:35Z</updated>
<entry>
<title>staging: lustre: delete the filesystem from the tree.</title>
<updated>2018-06-05T17:22:35Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2018-06-01T08:59:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=be65f9ed267fd7d8b3146b7c4be9ecdd3e0aa3ed'/>
<id>urn:sha1:be65f9ed267fd7d8b3146b7c4be9ecdd3e0aa3ed</id>
<content type='text'>
The Lustre filesystem has been in the kernel tree for over 5 years now.
While it has been an endless source of enjoyment for new kernel
developers learning how to do basic codingstyle cleanups, as well as an
semi-entertaining source of bewilderment from the vfs developers any
time they have looked into the codebase to try to figure out how to port
their latest api changes to this filesystem, it has not really moved
forward into the "this is in shape to get out of staging" despite many
half-completed attempts.

And getting code out of staging is the main goal of that portion of the
kernel tree.  Code should not stagnate and it feels like having this
code in staging is only causing the development cycle of the filesystem
to take longer than it should.  There is a whole separate out-of-tree
copy of this codebase where the developers work on it, and then random
changes are thrown over the wall at staging at some later point in time.
This dual-tree development model has never worked, and the state of this
codebase is proof of that.

So, let's just delete the whole mess.  Now the lustre developers can go
off and work in their out-of-tree codebase and not have to worry about
providing valid changelog entries and breaking their patches up into
logical pieces.  They can take the time they have spend doing those
types of housekeeping chores and get the codebase into a much better
shape, and it can be submitted for inclusion into the real part of the
kernel tree when ready.

Cc: Oleg Drokin &lt;oleg.drokin@intel.com&gt;
Cc: Andreas Dilger &lt;andreas.dilger@intel.com&gt;
Cc: James Simmons &lt;jsimmons@infradead.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: lustre: acl: increase ACL entries limitation</title>
<updated>2018-05-31T16:55:36Z</updated>
<author>
<name>Fan Yong</name>
<email>fan.yong@intel.com</email>
</author>
<published>2018-05-29T14:21:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=6f17a0443972fb700dca7f0be882206ae23c27d6'/>
<id>urn:sha1:6f17a0443972fb700dca7f0be882206ae23c27d6</id>
<content type='text'>
Originally, the limitation of ACL entries is 32, that is not
enough for some use cases. In fact, restricting ACL entries
count is mainly for preparing the RPC reply buffer to receive
the ACL data. So we cannot make the ACL entries count to be
unlimited. But we can enlarge the RPC reply buffer to hold
more ACL entries. On the other hand, MDT backend filesystem
has its own EA size limitation. For example, for ldiskfs case,
if large EA enable, then the max ACL size is 1048492 bytes;
otherwise, it is 4012 bytes. For ZFS backend, such value is
32768 bytes. With such hard limitation, we can calculate how
many ACL entries we can have at most. This patch increases
the RPC reply buffer to match such hard limitation. For old
client, to avoid buffer overflow because of large ACL data
(more than 32 ACL entries), the MDT will forbid the old client
to access the file with large ACL data. As for how to know
whether it is old client or new, a new connection flag
OBD_CONNECT_LARGE_ACL is used for that.

Signed-off-by: Fan Yong &lt;fan.yong@intel.com&gt;
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7473
Reviewed-on: https://review.whamcloud.com/19790
Reviewed-by: Andreas Dilger &lt;andreas.dilger@intel.com&gt;
Reviewed-by: Li Xi &lt;lixi@ddn.com&gt;
Reviewed-by: Lai Siyao &lt;lai.siyao@intel.com&gt;
Reviewed-by: Oleg Drokin &lt;oleg.drokin@intel.com&gt;
Signed-off-by: James Simmons &lt;jsimmons@infradead.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: lustre: libcfs: add parens around macros args</title>
<updated>2018-05-25T16:41:19Z</updated>
<author>
<name>Ivan Bornyakov</name>
<email>brnkv.i1@gmail.com</email>
</author>
<published>2018-05-22T13:34:39Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1e71247364a0805328eabc29fc627c808c88d3fe'/>
<id>urn:sha1:1e71247364a0805328eabc29fc627c808c88d3fe</id>
<content type='text'>
One may call 'CFS_FAIL_TIMEOUT(id, secs + 5);' and get unexpected result
after macro substitution, viz., 'secs + 5' will turn into
'secs + 5 * 1000'

Signed-off-by: Ivan Bornyakov &lt;brnkv.i1@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: lustre: Fix block comments style</title>
<updated>2018-05-25T16:40:56Z</updated>
<author>
<name>Sabin Mihai Rapan</name>
<email>sabin.rapan@gmail.com</email>
</author>
<published>2018-05-21T17:34:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=777690e68cbe27e266a746a9f5b63e273fe1a7a0'/>
<id>urn:sha1:777690e68cbe27e266a746a9f5b63e273fe1a7a0</id>
<content type='text'>
This patch fixes the checkpatch.pl warning:

WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line

Signed-off-by: Sabin Mihai Rapan &lt;sabin.rapan@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: lustre: Fix "unsigned"-&gt;"unsigned int"</title>
<updated>2018-05-25T16:40:56Z</updated>
<author>
<name>Sabin Mihai Rapan</name>
<email>sabin.rapan@gmail.com</email>
</author>
<published>2018-05-21T17:34:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=0fb1de16f391c2f726f950189204be5b90d08fb9'/>
<id>urn:sha1:0fb1de16f391c2f726f950189204be5b90d08fb9</id>
<content type='text'>
This patch fixes the checkpatch.pl warning:

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'

Signed-off-by: Sabin Mihai Rapan &lt;sabin.rapan@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: lustre: remove libcfs_all.h</title>
<updated>2018-05-25T16:36:43Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.com</email>
</author>
<published>2018-05-21T04:35:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=8e5566ac7300eb1f4268de22d616937bfe677db3'/>
<id>urn:sha1:8e5566ac7300eb1f4268de22d616937bfe677db3</id>
<content type='text'>
In the remaining files that include libcfs_all.h,
replace it with other include files as necessary,
then remove libcfs_all.h

Signed-off-by: NeilBrown &lt;neilb@suse.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: lustre: move all libcfs_all includes except in lustre/lnet/libcfs/</title>
<updated>2018-05-25T16:36:43Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.com</email>
</author>
<published>2018-05-21T04:35:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=7059b37ffe71420aab9c1d435df4e5f8c55b129b'/>
<id>urn:sha1:7059b37ffe71420aab9c1d435df4e5f8c55b129b</id>
<content type='text'>
Again, most of these are not needed.

Signed-off-by: NeilBrown &lt;neilb@suse.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: lustre: remove libcfs_all.h from remaining .h files.</title>
<updated>2018-05-25T16:36:18Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.com</email>
</author>
<published>2018-05-21T04:35:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=8f0ca7fca3ab4ab69b19e68e31f5c2e455cdc10d'/>
<id>urn:sha1:8f0ca7fca3ab4ab69b19e68e31f5c2e455cdc10d</id>
<content type='text'>
Now no *.h files include libcfs_all.h - only *.c files.

Signed-off-by: NeilBrown &lt;neilb@suse.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: lustre: remove libcfs_all.h from lustre/include/*.h</title>
<updated>2018-05-25T16:36:18Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.com</email>
</author>
<published>2018-05-21T04:35:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=73d65c8d1a851785af624870424b332f42af1b37'/>
<id>urn:sha1:73d65c8d1a851785af624870424b332f42af1b37</id>
<content type='text'>
Instead of the catch-all libcfs_all.h, just include the
files actually needed in different places.

Signed-off-by: NeilBrown &lt;neilb@suse.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>staging: lustre: don't include libcfs.h in lnet/lib-lnet.h</title>
<updated>2018-05-25T16:36:18Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.com</email>
</author>
<published>2018-05-21T04:35:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1f28db699f7cf8ac67f687410ba83c0eb202cc7f'/>
<id>urn:sha1:1f28db699f7cf8ac67f687410ba83c0eb202cc7f</id>
<content type='text'>
We want to be more focused in what is included where.
So we remove libcfs.h from where it isn't needed.

Signed-off-by: NeilBrown &lt;neilb@suse.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
