Re: [PATCH 2/2] binder: Use receive_fd() to receive file from another process

2021-04-15 Thread Al Viro
On Fri, Apr 16, 2021 at 05:19:50AM +, Al Viro wrote: > On Thu, Apr 01, 2021 at 12:40:34PM +0200, Christian Brauner wrote: > > and see whether all of them can be switched to simply using > > receive_fd(). I did a completely untested rough sketch to illustrate > > what I meant by using binder an

Re: [PATCH 2/2] binder: Use receive_fd() to receive file from another process

2021-04-15 Thread Al Viro
On Thu, Apr 01, 2021 at 12:40:34PM +0200, Christian Brauner wrote: > My suggestion was to look at all the places were we currently open-code > this in drivers/: > > drivers/android/binder.c: int fd = > get_unused_fd_flags(O_CLOEXEC); > drivers/char/tpm/tpm_vtpm_proxy.c: fd = ge

[driver-core:kbuild] BUILD SUCCESS 8e3809e7ff0a623e5cbb7130cd0fdc3507b76442

2021-04-15 Thread kernel test robot
lyesconfig powerpc allmodconfig powerpc allnoconfig x86_64 randconfig-a003-20210415 x86_64 randconfig-a002-20210415 x86_64 randconfig-a005-20210415 x86_64 randconfig-a001-20210

[driver-core:driver-core-testing] BUILD SUCCESS bd2a895f21eb9195a42e52e5f451dccc854cc71d

2021-04-15 Thread kernel test robot
allyesconfig mips allmodconfig powerpc allyesconfig powerpc allmodconfig powerpc allnoconfig x86_64 randconfig-a003-20210415 x86_64 randconfig-a002-20210415

[driver-core:debugfs_remove_return_value] BUILD SUCCESS 940ee39769474654d409e310fb43190221fa0b30

2021-04-15 Thread kernel test robot
powerpc allnoconfig x86_64 randconfig-a003-20210415 x86_64 randconfig-a002-20210415 x86_64 randconfig-a005-20210415 x86_64 randconfig-a001-20210415 x86_64 randconfig-a006-20210415 x86_64

[driver-core:readfile] BUILD SUCCESS 754793e73d5a800eb8bed0dc2068e26529615d07

2021-04-15 Thread kernel test robot
allmodconfig powerpc allnoconfig x86_64 randconfig-a003-20210415 x86_64 randconfig-a002-20210415 x86_64 randconfig-a005-20210415 x86_64 randconfig-a001-20210415 x86_64 randconfig-a006

[staging:staging-testing] BUILD REGRESSION 71d3edc61e29e45b613b841108688d711846f969

2021-04-15 Thread kernel test robot
alpha-allyesconfig | `-- drivers-comedi-drivers-jr3_pci.c:warning:variable-min_full_scale-set-but-not-used |-- alpha-randconfig-r034-20210415 | `-- drivers-comedi-drivers-jr3_pci.c:warning:variable-min_full_scale-set-but-not-used |-- arc-allyesconfig | `-- drivers-comedi-drivers-jr3_pci.c:warning:variable-min_f

[staging:staging-testing 704/705] drivers/comedi/drivers/jr3_pci.c:507:22: warning: variable 'min_full_scale' set but not used

2021-04-15 Thread kernel test robot
config: parisc-randconfig-r022-20210415 (attached as .config) compiler: hppa-linux-gcc (GCC) 9.3.0 reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # https

[staging:staging-testing 704/705] drivers/comedi/drivers/comedi_isadma.c:25:10: error: implicit declaration of function 'claim_dma_lock'

2021-04-15 Thread kernel test robot
config: m68k-randconfig-r006-20210415 (attached as .config) compiler: m68k-linux-gcc (GCC) 9.3.0 reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # https

[staging:staging-testing] BUILD SUCCESS 467d98420936009a10ce7f95985dece7150acd36

2021-04-15 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-testing branch HEAD: 467d98420936009a10ce7f95985dece7150acd36 staging: rtl8723bs: remove unused argument in function elapsed time: 720m configs tested: 159 configs skipped: 2 The following configs have bee