I'm announcing the release of the 4.4.133 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
Hi,
On 5/26/2018 3:37 AM, Douglas Anderson wrote:
> It appears that a "#define DEBUG" was left in on the recent patch
> landed for the Qualcomm DWC3 glue driver. Let's remove it.
>
> Fixes: a4333c3a6ba9 ("usb: dwc3: Add Qualcomm DWC3 glue driver")
> Signed-off-by: Douglas Anderson
> ---
>
> dr
On Sat, May 26, 2018 at 01:11:11AM +0100, Al Viro wrote:
> On Wed, May 23, 2018 at 09:19:49PM +0200, Christoph Hellwig wrote:
> > Hi all,
> >
> > this series adds support for the IOCB_CMD_POLL operation to poll for the
> > readyness of file descriptors using the aio subsystem. The API is based
>
I'm still waking up..
On Sat, May 12, 2018 at 10:43:08AM +0200, Dmitry Vyukov wrote:
> On Fri, Feb 2, 2018 at 11:18 PM, Eric Biggers wrote:
> > On Fri, Feb 02, 2018 at 02:57:32PM +0100, Dmitry Vyukov wrote:
> >> On Fri, Feb 2, 2018 at 2:48 PM, syzbot
> >> wrote:
> >> > Hello,
> >> >
> >> > syzbot hit the following cra
consider such situation, current user_policy.min is 100,
current user_policy.max is 120, in cpufreq_set_policy,
other driver may update policy.min to 120, policy.max to
130. After that, If we input "echo 130 > scaling_min_freq",
then user_policy.min will be 130, and user_pol
On 2018/5/25 5:43, Jason Gunthorpe wrote:
> On Wed, May 23, 2018 at 06:16:26PM +0800, Wei Hu (Xavier) wrote:
>> This patchset included fixing bug, some optimization, reset
>> process for hns driver.
>>
>> v1->v2: 1.pull the patch out of the series. The name of the patch is
>>RDMA/hns: Im
On Sat, May 26, 2018 at 10:25 AM, YueHaibing wrote:
> On 2018/5/26 0:19, Alexei Starovoitov wrote:
>> On Fri, May 25, 2018 at 06:17:57PM +0800, YueHaibing wrote:
>>> gcc-7.3.0 report following err:
>>>
>>> HOSTCC net/bpfilter/main.o
>>> In file included from net/bpfilter/main.c:9:0:
>>> ./inclu
syzbot has found a reproducer for the following crash on:
HEAD commit:e52cde717093 net: dsa: dsa_loop: Make dynamic debugging he..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1424a4b780
kernel config: https://syzkaller.appspot.com/x/.config?x=e40789
This patch hoisted the common process of disassociate_ucontext
callback function into ib core code, and these code are common
to ervery ib_device driver.
Signed-off-by: Wei Hu (Xavier)
---
drivers/infiniband/core/uverbs_main.c | 45 ++-
drivers/infiniband/hw/mlx4/
zone_align_start_offset should be u64, but config.start_sector is u32,
so it may be overflow when computing zone_align_start_offset.
Signed-off-by: Yunlong Song
---
fsck/resize.c | 7 ---
mkfs/f2fs_format.c | 4 ++--
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/fsck/re
This patch implemented the IB core disassociate_ucontext API.
Signed-off-by: Wei Hu (Xavier)
---
v2->v3: Addressed the comments from Jason. The related link:
https://lkml.org/lkml/2018/5/22/967
v1->v2: no change.
---
drivers/infiniband/hw/hns/hns_roce_device.h | 8
drivers/infinib
Hi, Jason and Doug
This patchset included fixing bug, reset process, and
implementation of the disassociate_ucontext API for hns
driver.
We refactored the implemetion of disaacociate_ucontext
in V1 series according to Jason's comment. The related
link: https://lkml.org/lkml/2018/5/22/967
Thanks.
This patch fixed the potential illegal operation when using the
extend sge buffer cross page in post send operation. The bug
will cause the calltrace as below.
[ 3302.922107] Unable to handle kernel paging request at virtual address
3b3a0004
[ 3302.930009] Mem abort info:
[ 3302.932790]
This patch added reset process for RoCE in hip08.
Signed-off-by: Wei Hu (Xavier)
--
v2->v3: no change.
v1->v2: 1.Delete handle->priv = NULL in hns_roce_hw_v2_uninit_instance.
2.Add hns_roce_hw_v2_reset_notify_init callback function,
When RoCE reinit failed in this function, inf
There were numerous coding syle errors in this file where spaces were required
around operators.
Signed-off-by: John Whitmore
---
.../staging/rtl8192u/ieee80211/rtl819x_HTProc.c| 126 ++---
1 file changed, 63 insertions(+), 63 deletions(-)
diff --git a/drivers/staging/rtl819
Correct the coding style of parenthesis and braces in various code blocks
Signed-off-by: John Whitmore
---
.../staging/rtl8192u/ieee80211/rtl819x_HTProc.c| 217 -
1 file changed, 79 insertions(+), 138 deletions(-)
diff --git a/drivers/staging/rtl8192u/ieee80211/rtl819x_H
five patches with simple coding style changes to the file
drivers/staging/rtl8192u/ieee80211/rtl819x_HTProc.c
The last two patches should probably have been combined as both dealt with the
addition or removal of blank lines, but I missed one style issue on the first
pass. In that situation I guess
Two switch statements had wrong indentation of 'case' options
Signed-off-by: John Whitmore
---
.../staging/rtl8192u/ieee80211/rtl819x_HTProc.c| 48 +++---
1 file changed, 24 insertions(+), 24 deletions(-)
diff --git a/drivers/staging/rtl8192u/ieee80211/rtl819x_HTProc.c
b/dr
Coding style requires blank line after definitions and function definition,
blank lines removed. Correction of some indentation.
Signed-off-by: John Whitmore
---
.../staging/rtl8192u/ieee80211/rtl819x_HTProc.c| 96 --
1 file changed, 34 insertions(+), 62 deletions(-)
dif
Missed these in the last pass. Coding style does not require blank line after
opening brace of a function.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/ieee80211/rtl819x_HTProc.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/staging/rtl8192u/ieee80211/rtl819x_HTPro
ping...
On 2018/5/7 10:15, Yunlong Song wrote:
f2fs-tools uses ioctl BLKSSZGET to get sector_size, however, this ioctl
will return a value which may be larger than 512 (according to the value
of q->limits.logical_block_size), then this will be inconsistent with
the start_sector, since start_sect
/rtmutex-allow-specifying-a-subclass-for-nested-locking/20180526-140421
config: x86_64-randconfig-i0-201820 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by
/rtmutex-allow-specifying-a-subclass-for-nested-locking/20180526-140421
config: x86_64-randconfig-x003-201820 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the
linux-review/Peter-Rosin
Hi,
On 25/05/2018 23:10, Olof Johansson wrote:
> On Fri, May 25, 2018 at 11:10:01AM +0530, Viresh Kumar wrote:
>> The cooling device properties, like "#cooling-cells" and
>> "dynamic-power-coefficient", should either be present for all the CPUs
>> of a cluster or none. If these are present only fo
Hi Abhishek,
On Fri, 25 May 2018 17:51:34 +0530, Abhishek Sahu
wrote:
> Currently the driver uses the ECC strength specified in DT.
> The QPIC/EBI2 NAND supports 4 or 8-bit ECC correction. The same
> kind of board can have different NAND parts so use the ECC
> strength from device parameters if
Hi Abhishek,
On Fri, 25 May 2018 17:51:29 +0530, Abhishek Sahu
wrote:
> commit 2c8f8afa7f92 ("mtd: nand: add generic helpers to check,
> match, maximize ECC settings") provides generic helpers which
> drivers can use for setting up ECC parameters.
>
> Since same board can have different ECC str
Hi Abhishek,
On Fri, 25 May 2018 17:51:31 +0530, Abhishek Sahu
wrote:
> If nand-ecc-strength specified in DT, then controller will use
> this ECC strength otherwise ECC strength will be calculated
> according to chip requirement and available OOB size.
>
> Signed-off-by: Abhishek Sahu
> ---
>
Hi Abhishek,
On Fri, 25 May 2018 17:51:40 +0530, Abhishek Sahu
wrote:
> Fix value returned by ->read_page_raw() to be the
> actual operation status, instead of always 0.
>
> Signed-off-by: Abhishek Sahu
> ---
Acked-by: Miquel Raynal
Hi Abhishek,
On Fri, 25 May 2018 17:51:33 +0530, Abhishek Sahu
wrote:
> QCOM NAND controller supports only one step size (512) so
> nand-ecc-step-size DT property is redundant. This property
> can be removed and ecc step size can be assigned with 512 value.
>
> Signed-off-by: Abhishek Sahu
> -
Hi Abhishek,
On Fri, 25 May 2018 17:51:35 +0530, Abhishek Sahu
wrote:
> The BAM has 3 channels - tx, rx and command. command channel
> is used for register read/writes, tx channel for data writes
> and rx channel for data reads. Currently, the driver assumes the
> transfer completion once it get
Hi Abhishek,
On Fri, 25 May 2018 17:51:41 +0530, Abhishek Sahu
wrote:
> The QCOM NAND controller layout is such that, the bad block byte
> offset for last codeword will come to first byte in spare area.
"is the first spare byte"?
> Currently, the raw read for last codeword is being done with
Hello,
syzbot found the following crash on:
HEAD commit:3fb48d881dbe Merge branch 'bpf-fib-mtu-check'
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15fc197780
kernel config: https://syzkaller.appspot.com/x/.config?x=b632d8e2c2ab2c1
dashboard link: ht
Hi Abhishek,
> @@ -2141,12 +2127,10 @@ static int qcom_nandc_block_bad(struct mtd_info *mtd,
> loff_t ofs)
> goto err;
> }
>
> - bbpos = mtd->writesize - host->cw_size * (ecc->steps - 1);
> -
> - bad = nandc->data_buffer[bbpos] != 0xff;
> + bad = bbm_bytes_buf[0
Hi Abhishek,
On Fri, 25 May 2018 17:51:42 +0530, Abhishek Sahu
wrote:
> Currently there is no error checking for raw read. For raw
> reads, there won’t be any ECC failure but the operational
> failures are possible, so schedule the NAND_FLASH_STATUS read
> after each codeword.
>
> Signed-off-by
Hello,
syzbot found the following crash on:
HEAD commit:fd0bfa8d6e04 Merge branch 'bpf-af-xdp-cleanups'
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11da942780
kernel config: https://syzkaller.appspot.com/x/.config?x=b632d8e2c2ab2c1
dashboard link:
Hello,
syzbot found the following crash on:
HEAD commit:203ec2fed17a Merge tag 'armsoc-fixes' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14feff9780
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b4e30da84ec1ed
da
Hello,
syzbot found the following crash on:
HEAD commit:62c8a069b510 net: mvpp2: Add missing VLAN tag detection
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10ad582780
kernel config: https://syzkaller.appspot.com/x/.config?x=b632d8e2c2ab2c1
dashboar
Hello,
syzbot found the following crash on:
HEAD commit:203ec2fed17a Merge tag 'armsoc-fixes' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14f0d5a780
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b4e30da84ec1ed
da
Hello,
syzbot found the following crash on:
HEAD commit:305bb5521282 Merge tag 'selinux-pr-20180516' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=153eb40f80
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b4e30da84ec1ed
da
Hello,
syzbot found the following crash on:
HEAD commit:62d18ecfa641 Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1093ccb780
kernel config: https://syzkaller.appspot.com/x/.config?x=982e2df1b9e60b02
da
Hello,
syzbot found the following crash on:
HEAD commit:62d18ecfa641 Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13e030d780
kernel config: https://syzkaller.appspot.com/x/.config?x=982e2df1b9e60b02
da
/commits/Marek-Vasut/mfd-da9063-Rename-PMIC_DA9063-to-PMIC_CHIP_ID_DA9063/20180526-162613
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
config: x86_64-randconfig-x002-201820 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the
Hello,
syzbot found the following crash on:
HEAD commit:75bc37fefc44 Linux 4.17-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=161de3c780
kernel config: https://syzkaller.appspot.com/x/.config?x=31f4b3733894ef79
dashboard link: https://syzkaller.a
#syz dup: KASAN: use-after-free Write in irq_bypass_register_consumer
On Wed, Nov 1, 2017 at 9:18 PM, Dmitry Vyukov wrote:
> On Wed, Nov 1, 2017 at 11:17 PM, syzbot
>
> wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> aae4e7a8bc44722fe70d58920a36916b1043195e
>> git://git.kernel.org
#syz dup: KASAN: use-after-free Write in irq_bypass_register_consumer
On Mon, May 21, 2018 at 7:25 PM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:0b449a441dac Merge tag 'dmaengine-fix-4.17-rc6' of git://g..
> git tree: upstream
> console output: http
#syz dup: KASAN: use-after-free Write in irq_bypass_register_consumer
On Sat, May 26, 2018 at 11:17 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:75bc37fefc44 Linux 4.17-rc4
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.
On Sun, May 13, 2018 at 8:21 AM, Eric Biggers wrote:
> On Thu, Apr 05, 2018 at 08:15:24PM -0700, Eric Biggers wrote:
>> On Mon, Jan 29, 2018 at 01:29:48PM +0800, Tianyu Lan wrote:
>> >
>> >
>> > On 1/27/2018 7:27 AM, Eric Biggers wrote:
>> > > On Sat, Dec 16, 2017 at 04:37:02PM +0800, Lan, Tianyu
#syz dup: KASAN: use-after-free Read in do_general_protection
On Sat, May 26, 2018 at 11:16 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:62d18ecfa641 Merge tag 'arm64-fixes' of git://git.kernel.o..
> git tree: upstream
> console output: https://syz
#syz dup: KASAN: use-after-free Read in do_general_protection
On Sun, May 13, 2018 at 4:21 PM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:036db8bd9637 Merge branch 'for-4.17-fixes' of git://git.ke..
> git tree: upstream
> console output: https://syzk
#syz dup: KASAN: use-after-free Read in do_general_protection
On Sat, May 26, 2018 at 11:13 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:203ec2fed17a Merge tag 'armsoc-fixes' of git://git.kernel...
> git tree: upstream
> console output: https://syz
#syz dup: KASAN: use-after-free Read in do_general_protection
On Thu, Apr 12, 2018 at 11:45 AM, syzbot
wrote:
> Hello,
>
> syzbot hit the following crash on upstream commit
> c18bb396d3d261ebbb4efbc05129c5d354c541e4 (Tue Apr 10 00:04:10 2018 +)
> Merge git://git.kernel.org/pub/scm/linux/kerne
-Rosin/rtmutex-allow-specifying-a-subclass-for-nested-locking/20180526-140421
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
kernel/locking/locktorture.c:444:9:
On 23/05/2018 21:58:14+0200, Mathieu Malaterre wrote:
> Fix typo introduced for RTC_DRV_JZ4740 in commit 586655d278ba ("rtc:
> jz4740: make the driver buildable as a module again").
>
> Signed-off-by: Mathieu Malaterre
> ---
> drivers/rtc/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 delet
syzbot has found a reproducer for the following crash on:
HEAD commit:62d18ecfa641 Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14c6bf5780
kernel config: https://syzkaller.appspot.com/x/.config?x=982e2d
On Sat, May 26, 2018 at 11:16 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:62d18ecfa641 Merge tag 'arm64-fixes' of git://git.kernel.o..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=13e030d780
> kernel config:
The MMC framework requires the ocr_mask to be provided. Without it, the
SD card is not detected, especially on the hx4700 platform.
Signed-off-by: Robert Jarzmik
---
drivers/mfd/asic3.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/mfd/asic3.c b/drivers/mfd/asic3.c
index cf2e25a
The usb client of the hx4700 is not working because no platform data is
declared. Fix it by adding the missing call.
Signed-off-by: Robert Jarzmik
---
arch/arm/mach-pxa/hx4700.c | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/mach-pxa/hx4700.c b/arch/arm/mach-pxa/hx4700.c
index
The function alloc_dma_buffer() is called from ibmvmc_add_buffer(),
in which a spin lock be held here, so we should use GFP_ATOMIC when
a lock is held.
Fixes: 0eca353e7ae7 ("misc: IBM Virtual Management Channel Driver (VMC)")
Signed-off-by: Wei Yongjun
---
drivers/misc/ibmvmc.c | 2 +-
1 file ch
As what former drcmr -1 value meant, add a this as a default to each
channel, ie. that by default no requestor line is used.
This is specifically used for network drivers smc91x and smc911x, and
needed for their port to slave maps.
Cc: Arnd Bergmann
Signed-off-by: Robert Jarzmik
---
drivers/dm
us a note to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Marek-Vasut/mfd-da9063-Rename-PMIC_DA9063-to-PMIC_CHIP_ID_DA9063/20180526-162613
> base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
> for-mfd-next
> config:
On Mon, May 14, 2018 at 10:06:31AM +0200, Linus Walleij wrote:
> Instead of passing a global GPIO number for the enable GPIO, pass
> a descriptor looked up with the standard devm_gpiod_get_optional()
> call.
>
> This regulator supports passing platform data, but enable/sleep
> regulators are looke
On 20.05.2018 16:48, Dmitry Osipenko wrote:
> DMA requests must be blocked before resetting VDE HW, otherwise it is
> possible to get a memory corruption or a machine hang. Use the reset
> control provided by the Memory Controller to block DMA before resetting
> the VDE HW.
>
> Signed-off-by: Dmit
- f2fs_fill_super
- recover_fsync_data
- recover_data
- del_fsync_inode
- iput
- iput_final
- write_inode_now
- f2fs_write_inode
- f2fs_balance_fs
- f2fs_balance_fs_bg
- sync_dirty_inodes
With data_flush mount option, during recovery, in order
Introduce clear_radix_tree_dirty_tag to include common codes for cleanup.
Signed-off-by: Chao Yu
---
fs/f2fs/data.c | 11 +++
fs/f2fs/dir.c| 8 +---
fs/f2fs/f2fs.h | 1 +
fs/f2fs/inline.c | 7 +--
fs/f2fs/node.c | 12 ++--
5 files changed, 16 insertions(+), 2
/rtmutex-allow-specifying-a-subclass-for-nested-locking/20180526-140421
config: i386-randconfig-s0-201820 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by
The bcm2835-mailbox returns NULL instead of an error pointer, which could
result in a NULL ptr dereference in mbox_request_channel. So fix this
by returning a proper error pointer.
Signed-off-by: Stefan Wahren
Fixes: 0bae6af6d704 ("mailbox: Enable BCM2835 mailbox support")
---
drivers/mailbox/bc
/Marek-Vasut/mfd-da9063-Rename-PMIC_DA9063-to-PMIC_CHIP_ID_DA9063/20180526-162613
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
config: x86_64-randconfig-x011-201820 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Friday, May 25, 2018 2:52 AM
> To: Vadim Pasternak
> Cc: andy.shevche...@gmail.com; gre...@linuxfoundation.org; linux-
> ker...@vger.kernel.org; platform-driver-...@vger.kernel.org; j...@resnulli.us;
> Michael
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Friday, May 25, 2018 3:31 AM
> To: Vadim Pasternak
> Cc: andy.shevche...@gmail.com; gre...@linuxfoundation.org; linux-
> ker...@vger.kernel.org; platform-driver-...@vger.kernel.org; j...@resnulli.us;
> Michael
No neet to change zone_align_start_offset to u64, because
zone_align_start_offset is always
smaller than zone_size_bytes, which is u32.
Thanks,
Junling
On 2018/5/26 16:09, Yunlong Song wrote:
> zone_align_start_offset should be u64, but config.start_sector is u32,
> so it may be overflow when co
the message be freed immediately, no need to trim it
back to the previous size.
Inspired by commit 7a9b3ec1e19f ("nl80211: remove unnecessary genlmsg_cancel()
calls")
Signed-off-by: YueHaibing
---
drivers/net/team/team.c | 2 --
drivers/net/wireless/mac80211_hwsim.c | 1 -
net/
Em Fri, May 25, 2018 at 05:19:54PM -0700, Stephane Eranian escreveu:
> Hi,
>
>
> With the latest tip.git perf, if you run
>
> $ perf record -a -o - sleep 2 | perf inject -b -i - | perf buildid-list -i -
> SEGFAULT in perf inject:
> free_dup_event (oe=0x55d25b88, oe=0x55d25b88,
> event=0x
On Fri, May 25, 2018 at 01:45:11PM -0700, Alexei Starovoitov wrote:
> On Fri, May 18, 2018 at 03:07:29PM +0100, Sean Young wrote:
> > Add support for BPF_PROG_LIRC_MODE2. This type of BPF program can call
> > rc_keydown() to reported decoded IR scancodes, or rc_repeat() to report
> > that the last
Em Fri, May 25, 2018 at 05:19:54PM -0700, Stephane Eranian escreveu:
>
> With the latest tip.git perf, if you run
>
> $ perf record -a -o - sleep 2 | perf inject -b -i - | perf buildid-list -i -
> SEGFAULT in perf inject:
I'm not being able to reproduce this problem here:
[root@seventh ~]# perf
Hi Peter,
I am seeing a new warning in dmesg on my Mac Mini G4 (ppc32), which
seems to refer to commit 85f1abe0019fc (*). Does this means there is
an issue on my setup ?
Thanks,
(*)
[0.006350] MPC7450 family performance monitor hardware support registered
[0.007544] WARNING: CPU: 0 PID:
ase drop us a note to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Souptick-Joarder/gpu-drm-gma500-Change-return-type-to-vm_fault_t/20180526-084629
> base: git://people.freedesktop.org/~airlied/linux.git drm-next
> config: x86_64-rand
From: Colin Ian King
The WCH CH382L PCIe adapter has 1 parallel port but unlike the similar
WCH CH328 adapter there are no serial ports connected to it. Enable
this adapter with the addition of the appropriate PCIe IDs and board
support config.
PCIe device ID 1c00:3050:
02:00.0 Serial controll
From: Colin Ian King
Trivial fix to spelling mistake in module description text.
Signed-off-by: Colin Ian King
---
drivers/media/platform/mtk-vpu/mtk_vpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/mtk-vpu/mtk_vpu.c
b/drivers/media/platform/mtk
]
url:
https://github.com/0day-ci/linux/commits/Michel-Pollet/dt-bindings-Add-the-r9a06g032-sysctrl-h-file/20180526-154235
base:
https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git
clk-renesas
reproduce:
# apt-get install sparse
make ARCH=x86_64
From: Colin Ian King
Trivial fix to spelling mistake in dev_warn message text
Signed-off-by: Colin Ian King
---
drivers/power/supply/max1721x_battery.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/power/supply/max1721x_battery.c
b/drivers/power/supply/max1721x_b
/0day-ci/linux/commits/Ross-Zwisler/Fix-DM-DAX-handling/20180526-212746
config: i386-randconfig-x014-201820 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by
Acked-by: Boris Pismenny
Thank you.
> -Original Message-
> From: Saeed Mahameed
> Sent: Saturday, May 26, 2018 2:19 AM
> To: da...@davemloft.net; a...@arndb.de; l...@kernel.org
> Cc: linux-kernel@vger.kernel.org; linux-r...@vger.kernel.org; Boris
> Pismenny ; Or Gerlitz ;
> Feras Daoud ;
2018-05-25 17:36+0200, Arnd Bergmann:
> The global ms_hyperv variable is part of the hyperv support, so
> we get a link error from accessing it in kernels that have this
> turned off:
>
> arch/x86/kvm/vmx.o: In function `alloc_loaded_vmcs':
> vmx.c:(.text+0x1654a): undefined reference to `ms_hyper
The Reset Controller should be registered in the end of probe, otherwise
Memory Controller device goes away if IRQ requesting fails and the Reset
Controller stays registered. To avoid having to unwind the MC probing in
a case of SMMU probe failure, let's simply print the error message without
faili
2018-05-21 10:52-0500, Brijesh Singh:
> On 05/19/2018 01:01 AM, Dan Carpenter wrote:
> > This is a fix from reviewing the code, but it looks like it might be
> > able to lead to an Oops. It affects 32bit systems.
> >
>
> Please note that SEV is not available on 32bit systems.
Added this note an
DMA requests must be blocked before resetting VDE HW, otherwise it is
possible to get a memory corruption or a machine hang. Use the reset
control provided by the Memory Controller to block DMA before resetting
the VDE HW.
Signed-off-by: Dmitry Osipenko
---
Changelog:
v2:
- Reset HW eve
2018-05-16 17:21+0200, Vitaly Kuznetsov:
> Changes since v3 [Radim Krcmar]:
> - PATCH2 fixing 'HV_GENERIC_SET_SPARCE_4K' typo added.
> - PATCH5 introducing kvm_make_vcpus_request_mask() API added.
> - Fix undefined behavior for hv->vp_index >= 64.
> - Merge kvm_hv_flush_tlb() and kvm_hv_flush_tlb_e
Recently binding of the Memory Controller has been extended, exposing
the Memory Client reset controls and hence it is now a reset controller.
Tegra video-decoder device is among the Memory Controller reset users,
document the new optional VDE HW reset property.
Signed-off-by: Dmitry Osipenko
---
From: Colin Ian King
Trivial fix to spelling mistake in pm8001_printk message text; also
I believe NOT_UNSUPPORTED should probably be NOT_SUPPORTED. Also
fix the indent of the pm8001_printk statement.
Signed-off-by: Colin Ian King
---
drivers/scsi/pm8001/pm8001_hwi.c | 2 +-
1 file changed, 1
On Sat, May 26, 2018 at 12:54:00AM +0300, Alexey Khoroshilov wrote:
> of_graph_get_next_endpoint() returns device_node with refcnt increased,
> but these is no of_node_put() for it.
I think this is correct - but would it not be simpler to do
endpoint = v4l2_fwnode_endpoint_alloc_parse(of_fwnod
Prevent a task from opening, in "write" mode, any /proc/*/mem
file that operates on the task's mm.
/proc/*/mem is mainly a debugging means and, as such, it shouldn't
be used by the inspected process itself.
Current implementation always allow a task to access its own
/proc/*/mem file.
A process can
2018-05-16 17:21+0200, Vitaly Kuznetsov:
> Hyper-V style PV TLB flush hypercalls inmplementation will use this API.
> To avoid memory allocation in CONFIG_CPUMASK_OFFSTACK case add
> cpumask_var_t argument.
>
> Signed-off-by: Vitaly Kuznetsov
> ---
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kv
From: Colin Ian King
Trivial fix to spelling mistake in dev_err message text
Signed-off-by: Colin Ian King
---
drivers/mfd/timberdale.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/timberdale.c b/drivers/mfd/timberdale.c
index 33abf5a79f2b..f49168fac223 10064
From: Colin Ian King
Trivial fix to spelling mistake in rsi_dbg message text
Signed-off-by: Colin Ian King
---
drivers/net/wireless/rsi/rsi_91x_mac80211.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/rsi/rsi_91x_mac80211.c
b/drivers/net/wireless/rsi
From: Colin Ian King
Trivial fix to spelling mistake in pr_err message text
Signed-off-by: Colin Ian King
---
drivers/target/target_core_transport.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/target/target_core_transport.c
b/drivers/target/target_core_transpor
From: Colin Ian King
Trivial fix to spelling mistake in pr_info message text
Signed-off-by: Colin Ian King
---
fs/9p/v9fs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/9p/v9fs.c b/fs/9p/v9fs.c
index 0429c8ee58f1..89bac3d2f05b 100644
--- a/fs/9p/v9fs.c
+++ b/fs/9p/v9f
From: Colin Ian King
Trivial fix to spelling mistake in string
Signed-off-by: Colin Ian King
---
sound/core/seq/seq_ports.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/core/seq/seq_ports.c b/sound/core/seq/seq_ports.c
index d21ece9f8d73..24d90abfc64d 100644
--- a/
On 05/11/2018 03:27 AM, Samuel Holland wrote:
> The Allwinner A64 SoC is known [1] to have an unstable architectural
> timer, which manifests itself most obviously in the time jumping forward
> a multiple of 95 years [2][3]. This coincides with 2^56 cycles at a
> timer frequency of 24 MHz, implying
From: Colin Ian King
Trivial fix to spelling mistake in hmi_error_types text
Signed-off-by: Colin Ian King
---
arch/powerpc/platforms/powernv/opal-hmi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/platforms/powernv/opal-hmi.c
b/arch/powerpc/platforms/power
1 - 100 of 196 matches
Mail list logo
