Fix page fault handling code to fixup r16-r18 registers.
Before the patch code had off-by-two registers bug.
This bug caused overwriting of ps,pc,gp registers instead
of fixing intended r16,r17,r18 (see `struct pt_regs`).
More details:
Initially Dmitry noticed a kernel bug as a failure
on strace
On Fri, 28 Dec 2018 at 17:18, Paweł Chmiel
wrote:
>
> This commit adds memory reservation required by MFC to run.
> On S5PV210 both regions needs to be on separate memory banks.
> Size of both regions is taken from stock sources.
>
> Signed-off-by: Paweł Chmiel
> ---
>
On Fri, 28 Dec 2018 at 17:18, Paweł Chmiel
wrote:
>
> Since we have separate compatible for our SOC,
> let's use it rather using one from exynos4210.
Please fix
your editor
to wrap lines
matching Linux
style because
it is difficult
to read.
You have unusual configuration because most of the
On 30.12.2018 18:48, Sam Ravnborg wrote:
> drmP.h is an relic from the days when there was a single header file.
> To enable the removal of drmP.h from all users drop include
> of drmP.h from bridge/dw_hdmi.h.
>
> A few files relied on the file included in drmP.h - add explicit
> include
> Slave mode driver is based on the concept of i2c-designware driver.
> +/*
> + * i2c slave support for Atmel's AT91 Two-Wire Interface (TWI)
> + *
> + * Copyright (C) 2017 Juergen Fitschen
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the
/0day-ci/linux/commits/Masahiro-Yamada/kbuild-remove-redundant-target-cleaning-on-failure/20181231-162816
base:
https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
for-next
config: x86_64-randconfig-r0-12311638 (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0
On Sun, Sep 23, 2018 at 10:14 AM Dmitry Vyukov wrote:
>
> On Sun, Sep 23, 2018 at 9:42 AM, syzbot
> wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:474ff2600889 net-ethtool: ETHTOOL_GUFO did not and should ..
> > git tree: net
> > console output:
Greetings dear, I contacted you few days ago but couldn’t get your
response; I like to share very vital information with you so do get
back to me.
On Mon, Dec 31, 2018 at 05:38:51PM +0800, joeyli wrote:
> Hi Greg,
>
> On Sun, Dec 30, 2018 at 03:48:35PM +0100, Greg Kroah-Hartman wrote:
> > On Sun, Dec 30, 2018 at 09:28:56PM +0800, Lee, Chun-Yi wrote:
> > > The wake lock/unlock sysfs interfaces check that the writer must has
> > >
/0day-ci/linux/commits/Masahiro-Yamada/kbuild-remove-redundant-target-cleaning-on-failure/20181231-162816
base:
https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
for-next
config: i386-randconfig-a1-201852 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
On Mon, Dec 31, 2018 at 05:41:05PM +0800, joeyli wrote:
> Hi Greg,
>
> Thanks for your review!
>
> On Sun, Dec 30, 2018 at 03:45:06PM +0100, Greg Kroah-Hartman wrote:
> > On Sun, Dec 30, 2018 at 09:28:54PM +0800, Lee, Chun-Yi wrote:
> > > There have some discussion in the following mail loop
On 12/31/18 2:11 AM, Takashi Iwai wrote:
On Mon, 31 Dec 2018 00:17:58 +0100,
Pierre-Louis Bossart wrote:
BTW, one thing I'd really like to avoid is to rearrange the probe
procedure of the legacy HDA driver (so that we can get codec_mask
during pci probe() call). The async probe is the result
On Sun 30-12-18 19:59:53, Shakeel Butt wrote:
> On Sun, Dec 30, 2018 at 12:00 AM Michal Hocko wrote:
> >
> > On Sun 30-12-18 08:45:13, Michal Hocko wrote:
> > > On Sat 29-12-18 11:34:29, Shakeel Butt wrote:
> > > > On Sat, Dec 29, 2018 at 2:06 AM Michal Hocko wrote:
> > > > >
> > > > > On Sat
Dear Linux folks,
Linux 4.19.13 from Debian Sid/unstable logs the message below on the
board MSI MS-7A37/B350M MORTAR with the processor AMD Ryzen 3 2200G.
As a result, the early time stamps do not seem to be working.
[0.00] Linux version 4.19.0-1-amd64
Hi MST and Jason,
Could you please take a look at this? This bug is caused by a thread
resizing the tun-queue (via tun_queue_resize -> ptr_ring_resize_multiple).
And error happens in tun_net_xmit -> ptr_ring_produce. My guess is bug
happens when reading r->queue in ptr_ring_produce.
I've look
Hi
I can't recreate these issue on my environment. I use gcc (Ubuntu
7.3.0-27ubuntu1~18.04) 7.3.0. Maybe there are some differenct between these
two compilers.
Do you have any idea how I should change this fragment of code:
sprintf(str, "%02x %02x %02x %02x %02x %02x %02x
Hi Greg,
Thanks for your review!
On Sun, Dec 30, 2018 at 03:45:06PM +0100, Greg Kroah-Hartman wrote:
> On Sun, Dec 30, 2018 at 09:28:54PM +0800, Lee, Chun-Yi wrote:
> > There have some discussion in the following mail loop about checking
> > capability in sysfs write handler:
> >
Hello,
syzbot found the following crash on:
HEAD commit:f346b0becb1b Merge branch 'akpm' (patches from Andrew)
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10f0bbdd40
kernel config: https://syzkaller.appspot.com/x/.config?x=c255c77ba370fe7c
On Sun, Dec 30, 2018 at 7:57 PM Sinan Kaya wrote:
>
> On Wed, Dec 26, 2018 at 12:41 PM Rafael J. Wysocki wrote:
> >
> > On Mon, Dec 24, 2018 at 12:26 AM Sinan Kaya wrote:
> > >
> > > Select IOSF_MBI only when PCI is set.
> > >
> > > Signed-off-by: Sinan Kaya
> > > ---
> > >
Hi Greg,
On Sun, Dec 30, 2018 at 03:48:35PM +0100, Greg Kroah-Hartman wrote:
> On Sun, Dec 30, 2018 at 09:28:56PM +0800, Lee, Chun-Yi wrote:
> > The wake lock/unlock sysfs interfaces check that the writer must has
> > CAP_BLOCK_SUSPEND capability. But the checking logic can be bypassed
> > by
arm, s390 and unicore32 use oneliner wrappers for memblock_alloc().
Replace their usage with direct call to memblock_alloc().
Suggested-by: Christoph Hellwig
Signed-off-by: Mike Rapoport
---
arch/arm/mm/mmu.c | 11 +++
arch/s390/numa/numa.c | 10 +-
There are several early memory allocations in arch/ code that use
memblock_phys_alloc() to allocate memory, convert the returned physical
address to the virtual address and then set the allocated memory to zero.
Exactly the same behaviour can be achieved simply by calling
memblock_alloc(): it
The pte_alloc_one_kernel() function allocates a page using
__get_free_page(GFP_KERNEL) when mm initialization is complete and
memblock_phys_alloc() on the earlier stages. The physical address of the
page allocated with memblock_phys_alloc() is converted to the virtual
address and in the both cases
Rather than use the memblock_alloc_base that returns a physical address and
then convert this address to the virtual one, use appropriate memblock
function that returns a virtual address.
There is a small functional change in the allocation of then NODE_DATA().
Instead of panicing if the local
Hi,
These patches simplify some of the early memory allocations by replacing
usage of older memblock APIs with newer and shinier ones.
Quite a few places in the arch/ code allocated memory using a memblock API
that returns a physical address of the allocated area, then converted this
physical
There are a several places that allocate memory using memblock APIs that
return a physical address, convert the returned address to the virtual
address and frequently also memset(0) the allocated range.
Update these places to use memblock allocators already returning a virtual
address. Use
Rather than use the memblock_alloc_base that returns a physical address and
then convert this address to the virtual one, use appropriate memblock
function that returns a virtual address.
Signed-off-by: Mike Rapoport
Tested-by: Michal Simek
---
arch/microblaze/mm/init.c | 5 +++--
1 file
On Sun, 2018-12-30 at 13:38 +, Colin King wrote:
> A return statement is not indented enough, fix this by adding the
> missing tab.
[]
> diff --git a/drivers/nfc/st95hf/core.c b/drivers/nfc/st95hf/core.c
[]
> @@ -672,7 +672,7 @@ static int st95hf_error_handling(struct st95hf_context
>
Thank you very much for this message, friend. We the people should
learn it and stop taking Cock of Conduct up our ass
пн, 31 дек. 2018 г. в 05:07, :
>
> Their take is that if you lent (licensed) them a lawnmower and told them
> not to wreck it, the fact that they did not wreck it entitles them
On Fri, Dec 28, 2018 at 11:00:02AM +0800, Pingfan Liu wrote:
> Customer reported a bug on a high end server with many pcie devices, where
> kernel bootup with crashkernel=384M, and kaslr is enabled. Even
> though we still see much memory under 896 MB, the finding still failed
> intermittently.
On 12/28/18 23:28, Stephen Boyd wrote:
Quoting Jorge Ramirez (2018-12-26 01:20:07)
On 12/18/18 15:35, Niklas Cassel wrote:
On Mon, Dec 17, 2018 at 03:37:43PM -0800, Stephen Boyd wrote:
Quoting Jorge Ramirez-Ortiz (2018-12-17 01:46:22)
Allow accessing the parent clock names required for the
On Fri, Dec 28, 2018 at 11:00:01AM +0800, Pingfan Liu wrote:
> The bottom-up allocation style is introduced to cope with movable_node,
> where the limit inferior of allocation starts from kernel's end, due to
> lack of knowledge of memory hotplug info at this early time. But if later,
> hotplug
On Mon, 31 Dec 2018 09:23:01 +0200
Tero Kristo wrote:
> On 28/12/2018 22:02, Tony Lindgren wrote:
> > * Andreas Kemnade [181227 20:13]:
> >> Hi,
> >>
> >> On Tue, 4 Dec 2018 08:45:57 -0800
> >> Tony Lindgren wrote:
> >>
> >>> * Andreas Kemnade [181204 06:17]:
> On Mon, 3 Dec 2018
The commands surrounded by ( ) are executed in a subshell, but in
most cases, we do not need to spawn an extra subshell.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/compressed/Makefile | 4 ++--
scripts/Makefile.build| 4 ++--
scripts/Makefile.lib | 28
Add PCIe Root Port support for Stratix10 device.
Main differences:
- HIP interface to access Root Port configuration register.
- TLP programming flow:
- One REG0 register
- Don't need to check alignment
Signed-off-by: Ley Foon Tan
---
drivers/pci/controller/Kconfig |2 +-
Since commit 9c2af1c7377a ("kbuild: add .DELETE_ON_ERROR special
target"), the target file is automatically deleted on failure.
The boilerplate code
... || { rm -f $@; false; }
is unneeded.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/Makefile| 2 +-
Add PCIe Root Port support for Stratix10 device and also update
device tree binding documentation.
v1 -> v2:
-
- Add define S10_TLP_FMTTYPE_* macros.
- Remove initialize structure members to NULL/zero.
- Rename *_funcs to *_data.
- Update comment and fix coding style warning from
Add support for altr,pcie-root-port-2.0.
Signed-off-by: Ley Foon Tan
---
.../devicetree/bindings/pci/altera-pcie.txt|4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/Documentation/devicetree/bindings/pci/altera-pcie.txt
Makefile does not need to calculate LINUX_VERSION_CODE.
Let's leave it to the preprocessor.
This commit changes include/generated/uapi/linux/version.h as follows:
Before:
#define LINUX_VERSION_CODE 267264
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))
After:
#define
On Mon, Dec 31, 2018 at 9:17 AM Tetsuo Handa
wrote:
>
> On 2018/12/31 16:49, Dmitry Vyukov wrote:
> > On Mon, Dec 31, 2018 at 8:42 AM syzbot
> > wrote:
> >>
> >> Hello,
> >>
> >> syzbot found the following crash on:
> >>
> >> HEAD commit:ef4ab8447aa2 selftests: bpf: install script
filechk_* rules often consist of multiple 'echo' lines. They must be
surrounded with { } or ( ) to work correctly. Otherwise, only the
string from the last 'echo' would be written into the target.
Let's take care of that in the 'filechk' in scripts/Kbuild.include
to clean up filechk_* rules.
On 2018/12/31 16:49, Dmitry Vyukov wrote:
> On Mon, Dec 31, 2018 at 8:42 AM syzbot
> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:ef4ab8447aa2 selftests: bpf: install script with_addr.sh
>> git tree: bpf-next
>> console output:
On Mon, 31 Dec 2018 00:17:58 +0100,
Pierre-Louis Bossart wrote:
>
> > BTW, one thing I'd really like to avoid is to rearrange the probe
> > procedure of the legacy HDA driver (so that we can get codec_mask
> > during pci probe() call). The async probe is the result of the many
> > struggles with
>From Desk of James Brown
Accountant officer Wema bank Of Nigeria
Hello My Dear ,
My name is James Brown I have decided to seek a confidential co-operation
with you in the execution of the deal described here-under for our both
mutual benefit and I hope you will keep it a top secret because
Hello,
syzbot found the following crash on:
HEAD commit:24894bc6eabc Merge branch 'neigh-get-support'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13ee4ddb40
kernel config: https://syzkaller.appspot.com/x/.config?x=1f6442435a55ea09
dashboard link:
Hello,
syzbot found the following crash on:
HEAD commit:38355a5f9a22 bnx2x: Fix NULL pointer dereference in bnx2x_..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=15fe167740
kernel config: https://syzkaller.appspot.com/x/.config?x=a91d685acb971514
Hi Marcel,
On 2018-12-31 11:34, Balakrishna Godavarthi wrote:
Hi Marcel,
On 2018-12-30 13:40, Marcel Holtmann wrote:
Hi Balakrishna,
Latest qualcomm chips are not sending an command complete event for
every firmware packet sent to chip. They only respond with a vendor
specific event for the
Hello,
syzbot found the following crash on:
HEAD commit:90cadbbf341d Merge git://git.kernel.org/pub/scm/linux/kern..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1018bf6740
kernel config: https://syzkaller.appspot.com/x/.config?x=f9a32c9a4aef9af7
201 - 248 of 248 matches
Mail list logo
