[PATCH 12/12] staging: lustre: llite: fixup return value ll_direct_IO_26

From: Dmitry Eremin Return the correct values from ll_direct_IO_26. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4069 Reviewed-on: http://review.whamcloud.com/8080 Reviewed-by: John L. Hammond Reviewed-by: James Simmons Reviewed-by: Oleg Drokin Signed-Off-

[PATCH 10/12] staging: lustre: llog: we don't need vfsmount

From: Lai Siyao The patch for LU-3286 removed vfsmount instances used on the server side. Since this is server side only we can remove it from the upstream client. Signed-off-by: Lai Siyao Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3286 Reviewed-on: http://review.whamcloud.com/8286 Rev

[PATCH 04/12] staging: lustre: ldlm: check all errors during ldlm_debugfs_setup()

From: Dmitry Eremin Fix ignoring errors from ldebugfs_add_vars() function. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3885 Reviewed-on: http://review.whamcloud.com/8115 Reviewed-by: John L. Hammond Reviewed-by: Andreas Dilger Signed-off-by: James Simmons

[PATCH 07/12] staging: lustre: libcfs: Fix NUMA emulated mode

From: Andriy Skulysh Kernel commit c1c3443c9c5e9be92641029ed229a41563e44506 assigns all allowed cpus to emulated node. End cpt initialization loop when all CPUs are assigned. Signed-off-by: Andriy Skulysh Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3992 Reviewed-on: http://review.whamc

[PATCH 11/12] staging: lustre: ptlrpc: initialize request session early

From: Mikhail Pershin Initialize request session early to make it available in high-priority handlers Signed-off-by: Mikhail Pershin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3467 Reviewed-on: http://review.whamcloud.com/7350 Reviewed-by: Alex Zhuravlev Reviewed-by: Fan Yong Reviewe

[PATCH 01/12] staging: lustre: obd: remove newline from LCONSOLE string

From: Amir Shehata Remove the newline from the LCONSOLE debug macro in the function class_config_dump_handler(). Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2149 Reviewed-on: http://review.whamcloud.com/4254 Reviewed-by: Alex Zhuravlev Reviewed-by: Andreas D

[PATCH 08/12] staging: lustre: llite: debugging for ll_file_open LASSERT

From: Andreas Dilger Add debugging for LASSERTF(it_disposition(it, DISP_ENQ_OPEN_REF) in ll_file_open(), since this is a rarely hit failure under racer, and it would be useful to get more information if this is hit again. Print the full intent disposition, as well as the status, in case Oleg's e

[PATCH 09/12] staging: lustre: llite: check ret of ll_prep_md_op_data in ll_dir_filler

From: Swapnil Pimpale ll_dir_filler() now checks the returned pointer from ll_prep_md_op_data() using IS_ERR() Signed-off-by: Swapnil Pimpale Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4082 Reviewed-on: http://review.whamcloud.com/8073 Reviewed-by: Dmitry Eremin Reviewed-by: John L. H

[PATCH 05/12] staging: lustre: obd: cleanup client import if client_obd_setup fails

From: Swapnil Pimpale client_obd_setup() allocates an obd_import which should be cleaned up if there is any failure afterwards in callers of client_obd_setup(). This patch fixes the bug in osc_setup(), mgc_setup(), mdc_setup() and lwp_setup(). The fix is to call obd_cleanup_client_import() before

[PATCH 00/12] staging: lustre: add patches from lustre 2.5.52 version

Assortment of bug fixes that are present in the 2.5.52 version of lustre that is missing in the upstream client. Amir Shehata (2): staging: lustre: obd: remove newline from LCONSOLE string staging: lustre: obd: add newline for dumped config record Andreas Dilger (1): staging: lustre: llite:

[PATCH 02/12] staging: lustre: obd: add newline for dumped config record

From: Amir Shehata The function class_config_parse_rec() parses the llog record and places it into a buffer to be returned. That buffer needs to end with a newline which is currently missing. Signed-off-by: Amir Shehata Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2149 Reviewed-on: http:

[PATCH 03/12] staging: lustre: ptlrpc: use unified handler for OST requests

From: Mikhail Pershin Switch OST/OFD request processing to the unified request handle. Signed-off-by: Mikhail Pershin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3467 Reviewed-on: http://review.whamcloud.com/7130 Reviewed-by: Andreas Dilger Reviewed-by: Alex Zhuravlev Signed-off-by: J

[PATCH 06/12] staging: lustre: fid: add a connect flag for open by FID

From: Lai Siyao Add OBD_CONNECT_OPEN_BY_FID for open by FID, if MDS supports this, for open by FID, it won't retry with name if object with the FID doesn't exist; while if client supports this, client won't pack name in open request if FID is known. Signed-off-by: Lai Siyao Intel-bug-id: https:

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

On 27-04-16 05:40, Jarkko Sakkinen wrote: >> The hardware supports calling EEXTEND on only a part of a page, I think the >> driver should also support that. > > Why would you want to do that? You might have segments in a binary that don't start at the beginning of a page or that end before the end

Re: [PATCH 05/15] staging: lustre: ldlm: use accessor macros for l_flags

Wow! I remember this stuff, even if from 3 years ago. Feels like a lifetime. Is this patch being applied to official Linux, hence this message? Xyratex collapsed, shed a mess of employees and sold the remnant to Seagate. Consequently, I don't really follow Lustre any more. Sorry. On 04/

[PATCH 13/15] staging: lustre: osc: Track number of "unstable" pages per osc

From: Prakash Surya This change adds simple accounting hooks for "unstable" pages on a per OSC basis. Now, in addition to the per filesystem tracking, each OSC will maintain a running total of its unstable pages. These counters are exported through the proc interface, and can be read using the lc

[PATCH 12/15] staging: lustre: osc: Track and limit "unstable" pages

From: Prakash Surya This change adds a global counter to track the number of "unstable" pages held by a given client, along with per file system counters. An "unstable" page is defined as a page which has been sent to the server as part of a bulk request, but is uncommitted to stable storage. In

[PATCH 14/15] staging: lustre: osc: Use SOFT_SYNC to urge server commit

From: Prakash Surya This change adds a BRW page flag, OBD_BRW_SOFT_SYNC. This flag is intended to urge a server to commit a client's unstable pages to stable storage. A client will add this flag to any BRW requests while it is in a state where it has "many" unstable pages pinned in its cache. Th

[PATCH 11/15] staging: lustre: mgc: fix 'error handling' issues

From: Sebastien Buisson Fix 'error handling' issues found by Coverity version 6.6.1: Unchecked return value (CHECKED_RETURN) Calling function without checking return value. Argument cannot be negative (NEGATIVE_RETURNS) Negative value used as argument to a function expecting a positive value. Si

[PATCH 07/15] staging: lustre: ldlm: remove code wireshark handling

From: Bruce Korb Wireshark output moved to userland file "lustre_dlm_flags_wshark.c" and only bits that can actually appear "on the wire" are emitted. The user land "packet-lustre.c" code that references these bits now gets emitted into that file. e.g. the "local_only" bit is never put on the wir

[PATCH 15/15] staging: lustre: ptlrpc: quiet warning for 2.1/2.5 connections

From: Andreas Dilger The Lustre 2.5.4 client will print a warning about connections with 2.1.3 servers, yet they are still supposed to be interoperable. Increase the window of warning to be up to Lustre 2.5.50, since we do not intend to allow interoperability between 2.1 and 2.6 systems. This was

[PATCH 06/15] staging: lustre: ldlm: clean up l_flags

From: Bruce Korb Remove the now obsolete LDLM_AST_FLAGS and LDLM_INHERIT_FLAGS defines. Remove the obsolete LDLM_FL_HIDE_LOCK_MASK define. Rename "local_only" mask to "off_wire" since it is confusingly similar to a flag that (I think) means, "do not copy this lock over the wire." Signed-off-by:

[PATCH 09/15] staging: lustre: llite: Replace printing of i_ino with ll_inode2fid()

From: James Nunez The printing of i_ino/i_generation in llite messages is not nearly so useful as printing the full inode FID, since i_ino is a "compressed" version of the FID and there may be duplicate values for i_ino in some cases (especially if running on a 32-bit client). All instances of p

[PATCH 00/15] patches missing from lustre 2.5.51

This is the collection of bug fixes and code cleanup that are missing from the upstream client that exist with lustre version 2.5.51. Andreas Dilger (1): staging: lustre: ptlrpc: quiet warning for 2.1/2.5 connections Bruce Korb (4): staging: lustre: ldlm: use accessor macros for l_flags sta

[PATCH 03/15] staging: lustre: obdclass: add LCT_SERVER_SESSION for server session

From: Wang Di Add LCT_SERVER_SESSION for server session, and separate the server session flag from LCT_SESSION, so to avoid allocating session info for client stack for each server request, if client and server are on the same node. Signed-off-by: Wang Di Intel-bug-id: https://jira.hpdd.intel.c

[PATCH 04/15] staging: lustre: lmv: kernel crash due to misconfigured MDT

From: Dmitry Eremin There are few places with access to lmv->tgts[] without check for NULL. Usually it may happens when MDT configured starting from index 1 instead of 0. For example: mkfs.lustre --reformat --mgs --mdt --index=1 /dev/sdd1 Signed-off-by: Dmitry Eremin Intel-bug-id: https

[PATCH 05/15] staging: lustre: ldlm: use accessor macros for l_flags

From: Bruce Korb Convert most of the ldlm lock's l_flags references from direct bit twiddling to using bit specific macros. A few multi-bit operations are left as an exercise for the reader. The changes are mostly in ldlm, but also in llite, osc and quota. Also add a multi-bit (mask) test. Sig

[PATCH 08/15] staging: lustre: ldlm: update comments about ldlm l_flags

From: Bruce Korb Add and update documentation about some of the ldlm l_flags. Signed-off-by: Bruce Korb Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2906 Reviewed-by: Keith Mannthey Reviewed-on: http://review.whamcloud.com/7963 Reviewed-by: Doug Oucharek Reviewed-by: Andreas Dilger Si

[PATCH 02/15] staging: lustre: llite: NFS reexport issue

From: Dmitry Eremin Suppress erroneous/confusing messages when NFS is out of sync and requests old data. Signed-off-by: Dmitry Eremin Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4050 Reviewed-on: http://review.whamcloud.com/7850 Reviewed-by: Andreas Dilger Reviewed-by: Bob Glossman Si

[PATCH 01/15] staging: lustre: llite: reset writeback index in ll_writepages

From: Jinshan Xiong Otherwise after one round the writeback index will become beyond the file size and ->writepages() turns into an empty operation. Also, a safety guard is added to limit the wait time for grant to 10 minutes(take recovery into consideration) at maximum in the osc_enter_cache()

[PATCH 10/15] staging: lustre: clio: add debug message in osc_completion()

From: Niu Yawei Replace LASSERT with LASSERTF in osc_completion, thus we can get more info when the LASSERT is triggered. Signed-off-by: Niu Yawei Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3843 Reviewed-on: http://review.whamcloud.com/7494 Reviewed-by: Bobi Jam Reviewed-by: Jinshan X

Re: [PATCH] vme: add vme_init_bridge for common bridge init

On 24/04/16 21:11, Aaron Sierra wrote: Consolidate vme_bridge structure setup that every bridge was required to do itself. This came about because .irq_mtx is only used within the VME core, but was required to be setup externally. This returns the structure passed in to support shorthand like

Re: [PATCH] vme: change LM callback argument to void pointer

Hi Aaron, On 24/04/16 00:03, Aaron Sierra wrote: Make the location monitor callback function prototype more useful by changing the argument from an integer to a void pointer. All VME bridge drivers were simply passing the location monitor index (e.g. 0-3) as the argument to these callbacks. It

Re: [PATCH 00/12] De-stage Sync File Framework

On Wed, Apr 27, 2016 at 01:27:07PM -0300, Gustavo Padovan wrote: > From: Gustavo Padovan > > Hi, > > This patchset sits on top of Sync ABI Rework v13: > > https://www.spinics.net/lists/dri-devel/msg105667.html > > The first eight clean up and prepare sync_file for de-staging. The last four > p

Re: [PATCH 12/12] Documentation: add Sync File doc

On Wed, Apr 27, 2016 at 01:27:19PM -0300, Gustavo Padovan wrote: > From: Gustavo Padovan > > Add sync_file documentation on dma-buf-sync_file.txt > --- > Documentation/dma-buf-sync_file.txt | 65 > + > 1 file changed, 65 insertions(+) > create mode 100644 Do

[PATCH 10/12] dma-buf/sync_file: de-stage sync_file

From: Gustavo Padovan sync_file is useful to connect one or more fences to the file. The file is used by userspace to track fences between drivers that share DMA bufs. Signed-off-by: Gustavo Padovan --- drivers/Kconfig | 2 ++ drivers/dma-buf/Kconfig

[PATCH 07/12] staging/android: improve documentation for sync_file

From: Gustavo Padovan num_fences was missing a colon mark and sync_file_create() now have better description. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync_file.c | 3 ++- drivers/staging/android/sync_file.h | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git

[PATCH 08/12] staging/android: style fix: alignment to match the open parenthesis

From: Gustavo Padovan Fix checks reported by checkpatch.pl. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync_file.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/android/sync_file.c b/drivers/staging/android/sync_file.c index 5d77c0

[PATCH 12/12] Documentation: add Sync File doc

From: Gustavo Padovan Add sync_file documentation on dma-buf-sync_file.txt --- Documentation/dma-buf-sync_file.txt | 65 + 1 file changed, 65 insertions(+) create mode 100644 Documentation/dma-buf-sync_file.txt diff --git a/Documentation/dma-buf-sync_file.tx

[PATCH 11/12] Documentation: include sync_file into DocBook

From: Gustavo Padovan Add entry in device-drivers.tmpl for sync_file documentation. Signed-off-by: Gustavo Padovan --- Documentation/DocBook/device-drivers.tmpl | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/DocBook/device-drivers.tmpl b/Documentation/DocBook/device-drive

[PATCH 05/12] staging/android: make sync_file_fdget() static

From: Gustavo Padovan There is no plan in the near future to use this function outside of this file so keep it as static. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync.c | 3 +-- drivers/staging/android/sync.h | 1 - 2 files changed, 1 insertion(+), 3 deletions(-) diff --git

[PATCH 09/12] dma-buf/sync_file: de-stage sync_file headers

From: Gustavo Padovan Move sync_file headers file to include/ dir. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync.h | 4 ++-- drivers/staging/android/sync_debug.c | 2 +- drivers/staging/android/sync_file.c

[PATCH 06/12] staging/android: prepare sync_file for de-staging

From: Gustavo Padovan Move its functions and structs to their own file. Also moves function's docs to the .c file. Signed-off-by: Gustavo Padovan --- drivers/staging/android/Makefile | 2 +- drivers/staging/android/sync.c | 373 --- drive

[PATCH 04/12] staging/android: make sync_file_merge() static

From: Gustavo Padovan There is no plan in the near future to use this function outside of this file so keep it as static. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync.c | 4 ++-- drivers/staging/android/sync.h | 2 -- 2 files changed, 2 insertions(+), 4 deletions(-) diff --

[PATCH 02/12] staging/android: drop sync_file_install() and sync_file_put()

From: Gustavo Padovan These two functions are just wrappers for one line functions, they call fd_install() and fput() respectively, so just get rid of them and use fd_install() and fput() directly for more simplicity. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync.c | 20

[PATCH 00/12] De-stage Sync File Framework

From: Gustavo Padovan Hi, This patchset sits on top of Sync ABI Rework v13: https://www.spinics.net/lists/dri-devel/msg105667.html The first eight clean up and prepare sync_file for de-staging. The last four patches do the de-staging, moving files to drivers/dma-buf/ and include/linux/ plus ad

[PATCH 01/12] staging/android: remove redundant comments on sync_merge_data

From: Gustavo Padovan struct sync_merge_data already have documentation on top of the struct definition. No need to duplicate it. Signed-off-by: Gustavo Padovan Reviewed-by: Maarten Lankhorst --- drivers/staging/android/uapi/sync.h | 10 +- 1 file changed, 5 insertions(+), 5 deletions

[PATCH 03/12] staging/android: move sync_file functions comments to sync.c

From: Gustavo Padovan To keep comments in line with drivers/dma-buf/ move all sync_file comments to sync.c. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync.c | 26 +- drivers/staging/android/sync.h | 31 --- 2 files changed, 2

Re: [PATCH] staging:xgifb: Fix Comparisons should place the constant on the right side of the test warning

On Wed, Apr 27, 2016 at 04:58:36PM +0300, Dan Carpenter wrote: On Wed, Apr 27, 2016 at 09:27:39AM -0400, YU Bo wrote: Fixed checkpatch.pl's warning 'Comparisons should place the constant on the right side of the test' Signed-off-by: YU Bo --- drivers/staging/xgifb/vb_setmode.c |4 ++-- 1

RE: [PATCH] staging: unisys: visorbus: initialize variables

> -Original Message- > From: David Kershner [mailto:david.kersh...@unisys.com] > Sent: Monday, April 18, 2016 10:40 PM > To: gre...@linuxfoundation.org; driverdev-devel@linuxdriverproject.org; > *S-Par-Maintainer > Cc: Binder, David Anthony ; Kershner, David A > > Subject: [PATCH] stagi

Re: [PATCH] staging:xgifb: Fix Comparisons should place the constant on the right side of the test warning

On Wed, Apr 27, 2016 at 04:58:36PM +0300, Dan Carpenter wrote: On Wed, Apr 27, 2016 at 09:27:39AM -0400, YU Bo wrote: Fixed checkpatch.pl's warning 'Comparisons should place the constant on the right side of the test' Signed-off-by: YU Bo --- drivers/staging/xgifb/vb_setmode.c |4 ++-- 1

Re: [PATCH 0/6] Intel Secure Guard Extensions

On Apr 27, 2016 1:18 AM, "Ingo Molnar" wrote: > > > * Andy Lutomirski wrote: > > > > What new syscalls would be needed for ssh to get all this support? > > > > This patchset or similar, plus some user code and an enclave to use. > > > > Sadly, on current CPUs, you also need Intel to bless the enc

Re: [PATCH] staging:xgifb: Fix Comparisons should place the constant on the right side of the test warning

On Wed, Apr 27, 2016 at 09:27:39AM -0400, YU Bo wrote: > Fixed checkpatch.pl's warning 'Comparisons should place the constant on > the right side of the test' > > Signed-off-by: YU Bo > --- > drivers/staging/xgifb/vb_setmode.c |4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > d

[PATCH] staging:xgifb: Fix Comparisons should place the constant on the right side of the test warning

Fixed checkpatch.pl's warning 'Comparisons should place the constant on the right side of the test' Signed-off-by: YU Bo --- drivers/staging/xgifb/vb_setmode.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/xgifb/vb_setmode.c b/drivers/staging/xgifb/

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

On Tue, Apr 26, 2016 at 11:49:38PM -0700, Jethro Beekman wrote: > On 25-04-16 10:34, Jarkko Sakkinen wrote: > > diff --git a/drivers/staging/intel_sgx/isgx_ioctl.c > b/drivers/staging/intel_sgx/isgx_ioctl.c > > new file mode 100644 > > index 000..9d8b36b > > --- /dev/null > > +++ b/drivers/stag

re: staging: add Lustre file system client support

Hello Lustre devs, The patch d7e09d0397e8: "staging: add Lustre file system client support" from May 2, 2013, leads to the following Parfait warning. Parfait is an Oracle static analysis tool. If there is a patch from this could you give credit to Lidza Louina ? drivers/staging/lustre/lustre/ldl

Re: [RFC v2 7/8] drm/fence: add fence timeline to drm_crtc

Hi, On 26 April 2016 at 00:33, Gustavo Padovan wrote: > +static inline struct drm_crtc *fence_to_crtc(struct fence *fence) > +{ > + if (fence->ops != &drm_crtc_fence_ops) > + return NULL; Since this is (currently) only used before unconditional dereferences, maybe turn this i

Re: [PATCH 0/6] Intel Secure Guard Extensions

* Andy Lutomirski wrote: > > What new syscalls would be needed for ssh to get all this support? > > This patchset or similar, plus some user code and an enclave to use. > > Sadly, on current CPUs, you also need Intel to bless the enclave. It looks > like > new CPUs might relax that requirem

Re: [PATCH 0/6] Intel Secure Guard Extensions

Hi! > > > Preventing cold boot attacks is really just icing on the cake. The > > > real point of this is to allow you to run an "enclave". An SGX > > > enclave has unencrypted code but gets access to a key that only it can > > > access. It could use that key to unwrap your ssh private key and s

Re: [PATCH 6/6] intel_sgx: TODO file for the staging area

On 26-04-16 04:23, Jarkko Sakkinen wrote: > In order to write test code I would need to use the SDK at minimum to > generate EINITTOKEN for the test enclave. You could do this right now with the Rust tools for SGX [1] [1] https://github.com/jethrogb/sgx-utils/ > /Jarkko Jethro