Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

On Sun, 27 May 2018, Michael Schmitz wrote: > That should have fixed the warning already ... It's still not fixed (hence my "acked-by" for Geunter's patch). --

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

On Sun, 27 May 2018, Michael Schmitz wrote: > That should have fixed the warning already ... It's still not fixed (hence my "acked-by" for Geunter's patch). --

Re: [PATCH 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

On Sat, May 26, 2018 at 10:56:52PM +0200, Greg Kroah-Hartman wrote: > On Sat, May 26, 2018 at 10:33:59PM +0200, Marcus Folkesson wrote: > > Signed-off-by: Marcus Folkesson > > I can't take patches without any changelog text. And why would you > submit a patch over

Re: [PATCH 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

On Sat, May 26, 2018 at 10:56:52PM +0200, Greg Kroah-Hartman wrote: > On Sat, May 26, 2018 at 10:33:59PM +0200, Marcus Folkesson wrote: > > Signed-off-by: Marcus Folkesson > > I can't take patches without any changelog text. And why would you > submit a patch over 1000 lines without any? I'm

Re: net-next boot error: KASAN: use-after-free Write in call_usermodehelper_exec_work

On Sun, May 27, 2018 at 7:34 AM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:5b79c2af667c Merge git://git.kernel.org/pub/scm/linux/kern.. > git tree: net-next > console output:

Re: net-next boot error: KASAN: use-after-free Write in call_usermodehelper_exec_work

On Sun, May 27, 2018 at 7:34 AM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:5b79c2af667c Merge git://git.kernel.org/pub/scm/linux/kern.. > git tree: net-next > console output: https://syzkaller.appspot.com/x/log.txt?x=16087fa780 > kernel config:

net-next boot error: KASAN: use-after-free Write in call_usermodehelper_exec_work

Hello, syzbot found the following crash on: HEAD commit:5b79c2af667c Merge git://git.kernel.org/pub/scm/linux/kern.. git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=16087fa780 kernel config: https://syzkaller.appspot.com/x/.config?x=e4078980b886800c

net-next boot error: KASAN: use-after-free Write in call_usermodehelper_exec_work

Hello, syzbot found the following crash on: HEAD commit:5b79c2af667c Merge git://git.kernel.org/pub/scm/linux/kern.. git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=16087fa780 kernel config: https://syzkaller.appspot.com/x/.config?x=e4078980b886800c

RE: [PATCH V4 0/3] Use efi_rts_wq to invoke EFI Runtime Services

> > Assume some user requested to execute some non-blocking variant of > > efi_rts and the kernel hasn't called efi_call_virt() yet, but was > > scheduled out. IOW, even though user requests for non-blocking efi call, we > might still block. Am I right? > > > > No, that is the whole point. These

RE: [PATCH V4 0/3] Use efi_rts_wq to invoke EFI Runtime Services

> > Assume some user requested to execute some non-blocking variant of > > efi_rts and the kernel hasn't called efi_call_virt() yet, but was > > scheduled out. IOW, even though user requests for non-blocking efi call, we > might still block. Am I right? > > > > No, that is the whole point. These

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

Hi Finn, was your patch to implement this in arch_setup_pdev_archdata() rejected? That should have fixed the warning already ... Am 27.05.2018 um 15:01 schrieb Finn Thain: > On Sat, 26 May 2018, Guenter Roeck wrote: > >> As of commit 205e1b7f51e4 ("dma-mapping: warn when there is no >>

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

Hi Finn, was your patch to implement this in arch_setup_pdev_archdata() rejected? That should have fixed the warning already ... Am 27.05.2018 um 15:01 schrieb Finn Thain: > On Sat, 26 May 2018, Guenter Roeck wrote: > >> As of commit 205e1b7f51e4 ("dma-mapping: warn when there is no >>

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

Hi, On Sun, May 27, 2018 at 01:01:11PM +1000, Finn Thain wrote: > On Sat, 26 May 2018, Guenter Roeck wrote: > > > As of commit 205e1b7f51e4 ("dma-mapping: warn when there is no > > coherent_dma_mask") the NatSemi SONIC Ethernet driver is issuing the > > following warning on driver initialization

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

Hi, On Sun, May 27, 2018 at 01:01:11PM +1000, Finn Thain wrote: > On Sat, 26 May 2018, Guenter Roeck wrote: > > > As of commit 205e1b7f51e4 ("dma-mapping: warn when there is no > > coherent_dma_mask") the NatSemi SONIC Ethernet driver is issuing the > > following warning on driver initialization

Re: [PATCH] powerpc/64s: Clear PCR on boot

Hi Michael, On Sun, May 27, 2018 at 12:22:23PM +1000, Michael Ellerman wrote: > > > On 25 May 2018 11:33:08 pm AEST, Guenter Roeck wrote: > >On Fri, May 18, 2018 at 11:37:42AM +1000, Michael Neuling wrote: > >> Clear the PCR (Processor Compatibility Register) on boot to

Re: [PATCH] powerpc/64s: Clear PCR on boot

Hi Michael, On Sun, May 27, 2018 at 12:22:23PM +1000, Michael Ellerman wrote: > > > On 25 May 2018 11:33:08 pm AEST, Guenter Roeck wrote: > >On Fri, May 18, 2018 at 11:37:42AM +1000, Michael Neuling wrote: > >> Clear the PCR (Processor Compatibility Register) on boot to ensure we > >> are not

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

On Sat, 26 May 2018, Guenter Roeck wrote: > As of commit 205e1b7f51e4 ("dma-mapping: warn when there is no > coherent_dma_mask") the NatSemi SONIC Ethernet driver is issuing the > following warning on driver initialization on Macintosh q800 systems. > > SONIC ethernet @50f0a000, MAC

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

On Sat, 26 May 2018, Guenter Roeck wrote: > As of commit 205e1b7f51e4 ("dma-mapping: warn when there is no > coherent_dma_mask") the NatSemi SONIC Ethernet driver is issuing the > following warning on driver initialization on Macintosh q800 systems. > > SONIC ethernet @50f0a000, MAC

Re: [PATCH] bdi: Fix another oops in wb_workfn()

On Sun, May 27, 2018 at 11:21:25AM +0900, Tetsuo Handa wrote: > From 8a8222698163d1fe180258566e9a3ff43f54fcd9 Mon Sep 17 00:00:00 2001 > From: Tetsuo Handa > Date: Sun, 27 May 2018 11:08:20 +0900 > Subject: [PATCH] bdi: Fix another oops in wb_workfn() > >

Re: [PATCH] bdi: Fix another oops in wb_workfn()

On Sun, May 27, 2018 at 11:21:25AM +0900, Tetsuo Handa wrote: > From 8a8222698163d1fe180258566e9a3ff43f54fcd9 Mon Sep 17 00:00:00 2001 > From: Tetsuo Handa > Date: Sun, 27 May 2018 11:08:20 +0900 > Subject: [PATCH] bdi: Fix another oops in wb_workfn() > > syzbot is still hitting NULL pointer

[RFC PATCH] regulator: bd71837: buck_7_volts[] can be static

Fixes: 9ebaeaf21446 ("regulator: bd71837: Build BD71837 regulator driver") Signed-off-by: kbuild test robot --- bd71837-regulator.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/regulator/bd71837-regulator.c

[RFC PATCH] regulator: bd71837: buck_7_volts[] can be static

Fixes: 9ebaeaf21446 ("regulator: bd71837: Build BD71837 regulator driver") Signed-off-by: kbuild test robot --- bd71837-regulator.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/regulator/bd71837-regulator.c b/drivers/regulator/bd71837-regulator.c index

Re: [PATCH 9/9] regulator: bd71837: Build BD71837 regulator driver

/linux/commits/Matti-Vaittinen/mfd-regulator-clk-bd71837-ROHM-BD71837-PMIC-driver/20180526-192351 base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__

Re: [PATCH 9/9] regulator: bd71837: Build BD71837 regulator driver

/linux/commits/Matti-Vaittinen/mfd-regulator-clk-bd71837-ROHM-BD71837-PMIC-driver/20180526-192351 base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__

[PATCH] bdi: Fix another oops in wb_workfn()

>From 8a8222698163d1fe180258566e9a3ff43f54fcd9 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Sun, 27 May 2018 11:08:20 +0900 Subject: [PATCH] bdi: Fix another oops in wb_workfn() syzbot is still hitting NULL pointer dereference at wb_workfn() [1]. This

[PATCH] bdi: Fix another oops in wb_workfn()

>From 8a8222698163d1fe180258566e9a3ff43f54fcd9 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Sun, 27 May 2018 11:08:20 +0900 Subject: [PATCH] bdi: Fix another oops in wb_workfn() syzbot is still hitting NULL pointer dereference at wb_workfn() [1]. This might be because we overlooked that

Re: [PATCH] powerpc/64s: Clear PCR on boot

On 25 May 2018 11:33:08 pm AEST, Guenter Roeck wrote: >On Fri, May 18, 2018 at 11:37:42AM +1000, Michael Neuling wrote: >> Clear the PCR (Processor Compatibility Register) on boot to ensure we >> are not running in a compatibility mode. >> >> We've seen this cause problems

Re: [PATCH] powerpc/64s: Clear PCR on boot

On 25 May 2018 11:33:08 pm AEST, Guenter Roeck wrote: >On Fri, May 18, 2018 at 11:37:42AM +1000, Michael Neuling wrote: >> Clear the PCR (Processor Compatibility Register) on boot to ensure we >> are not running in a compatibility mode. >> >> We've seen this cause problems when a crash (and

Re: [PATCH] proc: prevent a task from writing on its own /proc/*/mem

On Sat, May 26, 2018 at 5:32 PM Kees Cook wrote: > I went through some old threads from 2012 when e268337dfe26 was > introduced, and later when things got looked at during DirtyCOW. There > was discussion about removing FOLL_FORCE (in order to block writes on > a read-only

Re: [PATCH] proc: prevent a task from writing on its own /proc/*/mem

On Sat, May 26, 2018 at 5:32 PM Kees Cook wrote: > I went through some old threads from 2012 when e268337dfe26 was > introduced, and later when things got looked at during DirtyCOW. There > was discussion about removing FOLL_FORCE (in order to block writes on > a read-only memory region). Side

Re: [PATCH, net-next] qcom-emag: hide ACPI specific functions

On 5/25/18 7:22 PM, Timur Tabi wrote: -phy->open = emac_sgmii_open; -phy->close = emac_sgmii_close; -phy->link_up = emac_sgmii_link_up; -phy->link_down = emac_sgmii_link_down; I'll take it look at it next week when I'm back in the office. I posted a patch that fixes this

Re: [PATCH, net-next] qcom-emag: hide ACPI specific functions

On 5/25/18 7:22 PM, Timur Tabi wrote: -phy->open = emac_sgmii_open; -phy->close = emac_sgmii_close; -phy->link_up = emac_sgmii_link_up; -phy->link_down = emac_sgmii_link_down; I'll take it look at it next week when I'm back in the office. I posted a patch that fixes this

[PATCH 0/2] x86/numa_emulation: Introduce uniform split capability

The current numa emulation capabilities for splitting System RAM by a fixed size or by a set number of nodes may result in some nodes being larger than others. The implementation prioritizes establishing a minimum usable memory size over satisfying the requested number of numa nodes.

[PATCH 1/2] x86/numa_emulation: Fix emulated-to-physical node mapping

Without this change the distance table calculation for emulated nodes may use the wrong numa node and report an incorrect distance. Cc: Wei Yang Cc: David Rientjes Cc: Thomas Gleixner Cc: "H. Peter Anvin" Cc:

[PATCH 1/2] x86/numa_emulation: Fix emulated-to-physical node mapping

Without this change the distance table calculation for emulated nodes may use the wrong numa node and report an incorrect distance. Cc: Wei Yang Cc: David Rientjes Cc: Thomas Gleixner Cc: "H. Peter Anvin" Cc: Ingo Molnar Cc: Signed-off-by: Dan Williams --- arch/x86/mm/numa_emulation.c |

[PATCH 0/2] x86/numa_emulation: Introduce uniform split capability

The current numa emulation capabilities for splitting System RAM by a fixed size or by a set number of nodes may result in some nodes being larger than others. The implementation prioritizes establishing a minimum usable memory size over satisfying the requested number of numa nodes.

[PATCH 2/2] x86/numa_emulation: Introduce uniform split capability

The current numa emulation capabilities for splitting System RAM by a fixed size or by a set number of nodes may result in some nodes being larger than others. The implementation prioritizes establishing a minimum usable memory size over satisfying the requested number of numa nodes. Introduce a

[PATCH 2/2] x86/numa_emulation: Introduce uniform split capability

The current numa emulation capabilities for splitting System RAM by a fixed size or by a set number of nodes may result in some nodes being larger than others. The implementation prioritizes establishing a minimum usable memory size over satisfying the requested number of numa nodes. Introduce a

Re: WARNING: bad usercopy in __kvm_write_guest_page

On Sat, May 26, 2018 at 10:42 AM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:73fcb1a370c7 Merge branch 'akpm' (patches from Andrew) > git tree: upstream > console output:

Re: WARNING: bad usercopy in __kvm_write_guest_page

On Sat, May 26, 2018 at 10:42 AM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:73fcb1a370c7 Merge branch 'akpm' (patches from Andrew) > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=15b3a82780 > kernel config:

Re: general protection fault in wb_workfn (2)

Forwarding http://lkml.kernel.org/r/201805251915.fgh64517.hvfjoolffmq...@i-love.sakura.ne.jp . Jan Kara wrote: > > void delayed_work_timer_fn(struct timer_list *t) > > { > > struct delayed_work *dwork = from_timer(dwork, t, timer); > > > > /* should have been called from irqsafe timer

Re: general protection fault in wb_workfn (2)

Forwarding http://lkml.kernel.org/r/201805251915.fgh64517.hvfjoolffmq...@i-love.sakura.ne.jp . Jan Kara wrote: > > void delayed_work_timer_fn(struct timer_list *t) > > { > > struct delayed_work *dwork = from_timer(dwork, t, timer); > > > > /* should have been called from irqsafe timer

[PATCH v3] gpu: drm: gma500: Change return type to vm_fault_t

Use new return type vm_fault_t for fault handler. For now, this is just documenting that the function returns a VM_FAULT value rather than an errno. Once all instances are converted, vm_fault_t will become a distinct type. Ref-> commit 1c8f422059ae ("mm: change return type to vm_fault_t")

[PATCH v3] gpu: drm: gma500: Change return type to vm_fault_t

Use new return type vm_fault_t for fault handler. For now, this is just documenting that the function returns a VM_FAULT value rather than an errno. Once all instances are converted, vm_fault_t will become a distinct type. Ref-> commit 1c8f422059ae ("mm: change return type to vm_fault_t")

Re: [PATCH] proc: prevent a task from writing on its own /proc/*/mem

On Sat, May 26, 2018 at 7:50 AM, Salvatore Mesoraca wrote: > 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.

Re: [PATCH] proc: prevent a task from writing on its own /proc/*/mem

On Sat, May 26, 2018 at 7:50 AM, Salvatore Mesoraca wrote: > 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

[RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

As of commit 205e1b7f51e4 ("dma-mapping: warn when there is no coherent_dma_mask") the NatSemi SONIC Ethernet driver is issuing the following warning on driver initialization on Macintosh q800 systems. SONIC ethernet @50f0a000, MAC 08:00:07:12:34:56, IRQ 3 [ cut here ]

[RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

As of commit 205e1b7f51e4 ("dma-mapping: warn when there is no coherent_dma_mask") the NatSemi SONIC Ethernet driver is issuing the following warning on driver initialization on Macintosh q800 systems. SONIC ethernet @50f0a000, MAC 08:00:07:12:34:56, IRQ 3 [ cut here ]

Re: [PATCH v2] mm: fix race between kmem_cache destroy, create and deactivate

On Sat, May 26, 2018 at 11:58 AM, Vladimir Davydov wrote: > On Tue, May 22, 2018 at 01:13:36PM -0700, Shakeel Butt wrote: >> The memcg kmem cache creation and deactivation (SLUB only) is >> asynchronous. If a root kmem cache is destroyed whose memcg cache is in >> the

Re: [PATCH v2] mm: fix race between kmem_cache destroy, create and deactivate

On Sat, May 26, 2018 at 11:58 AM, Vladimir Davydov wrote: > On Tue, May 22, 2018 at 01:13:36PM -0700, Shakeel Butt wrote: >> The memcg kmem cache creation and deactivation (SLUB only) is >> asynchronous. If a root kmem cache is destroyed whose memcg cache is in >> the process of creation or

Re: [PATCH] memcg: force charge kmem counter too

On Sat, May 26, 2018 at 11:51 AM, Vladimir Davydov wrote: > On Fri, May 25, 2018 at 11:55:01AM -0700, Shakeel Butt wrote: >> Based on several conditions the kernel can decide to force charge an >> allocation for a memcg i.e. overcharge memcg->memory and memcg->memsw >>

Re: [PATCH] memcg: force charge kmem counter too

On Sat, May 26, 2018 at 11:51 AM, Vladimir Davydov wrote: > On Fri, May 25, 2018 at 11:55:01AM -0700, Shakeel Butt wrote: >> Based on several conditions the kernel can decide to force charge an >> allocation for a memcg i.e. overcharge memcg->memory and memcg->memsw >> counters. Do the same for

Re: [PATCH] ALSA: seq: fix spelling mistake "Unamed" -> "Unnamed"

On Sat, 26 May 2018 17:11:00 +0200, Colin King wrote: > > From: Colin Ian King > > Trivial fix to spelling mistake in string > > Signed-off-by: Colin Ian King Applied, thanks. Takashi

Re: [PATCH] ALSA: seq: fix spelling mistake "Unamed" -> "Unnamed"

On Sat, 26 May 2018 17:11:00 +0200, Colin King wrote: > > From: Colin Ian King > > Trivial fix to spelling mistake in string > > Signed-off-by: Colin Ian King Applied, thanks. Takashi

Re: [PATCH] ASoC: AMD: make channel 1 dma as circular

On Fri, May 25, 2018 at 3:23 AM Akshu Agrawal wrote: > channel 1: SYSMEM<->ACP > channel 2: ACP<->I2S > Instead of waiting on period interrupt of ch 2 and then starting > dma on ch1, we make ch1 dma as circular. > This removes dependency of period granularity on hw

Re: [PATCH] ASoC: AMD: make channel 1 dma as circular

On Fri, May 25, 2018 at 3:23 AM Akshu Agrawal wrote: > channel 1: SYSMEM<->ACP > channel 2: ACP<->I2S > Instead of waiting on period interrupt of ch 2 and then starting > dma on ch1, we make ch1 dma as circular. > This removes dependency of period granularity on hw pointer. > Signed-off-by:

[PATCH v2 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

Chip Card Interface Device (CCID) protocol is a USB protocol that allows a smartcard device to be connected to a computer via a card reader using a standard USB interface, without the need for each manufacturer of smartcards to provide its own reader or protocol. This gadget driver makes Linux

[PATCH v2 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

Chip Card Interface Device (CCID) protocol is a USB protocol that allows a smartcard device to be connected to a computer via a card reader using a standard USB interface, without the need for each manufacturer of smartcards to provide its own reader or protocol. This gadget driver makes Linux

[PATCH v2 2/3] Documentation: usb: add documentation for USB CCID Gadget Device

Add documentation to give a brief description on how to use the CCID Gadget Device. This includes a description for all attributes followed by an example on how to setup the device with ConfigFS. Signed-off-by: Marcus Folkesson --- Documentation/usb/gadget_ccid.rst |

[PATCH v2 2/3] Documentation: usb: add documentation for USB CCID Gadget Device

Add documentation to give a brief description on how to use the CCID Gadget Device. This includes a description for all attributes followed by an example on how to setup the device with ConfigFS. Signed-off-by: Marcus Folkesson --- Documentation/usb/gadget_ccid.rst | 267

[PATCH v2 3/3] MAINTAINERS: add USB CCID Gadget Device

Add MAINTAINERS entry for USB CCID Gadget Device Signed-off-by: Marcus Folkesson --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 078fd80f664f..e77c3d2bec89 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@

[PATCH v2 3/3] MAINTAINERS: add USB CCID Gadget Device

Add MAINTAINERS entry for USB CCID Gadget Device Signed-off-by: Marcus Folkesson --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 078fd80f664f..e77c3d2bec89 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -14541,6 +14541,14 @@ L:

[GIT PULL] ARM: SoC fixes

Hi Linus, Please merge. Thanks! -Olof The following changes since commit 771c577c23bac90597c685971d7297ea00f99d11: Linux 4.17-rc6 (2018-05-20 15:31:38 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-fixes for

[GIT PULL] ARM: SoC fixes

Hi Linus, Please merge. Thanks! -Olof The following changes since commit 771c577c23bac90597c685971d7297ea00f99d11: Linux 4.17-rc6 (2018-05-20 15:31:38 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-fixes for

Re: [PATCH 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

On Sat, May 26, 2018 at 10:33:59PM +0200, Marcus Folkesson wrote: > Signed-off-by: Marcus Folkesson I can't take patches without any changelog text. And why would you submit a patch over 1000 lines without any? Please fix. thanks, greg k-h

Re: [PATCH 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

On Sat, May 26, 2018 at 10:33:59PM +0200, Marcus Folkesson wrote: > Signed-off-by: Marcus Folkesson I can't take patches without any changelog text. And why would you submit a patch over 1000 lines without any? Please fix. thanks, greg k-h

Re: [GIT PULL] ARM: at91: DT for 4.18

On Sat, May 26, 2018 at 12:50:33AM +0200, Alexandre Belloni wrote: > Arnd, Olof, > > I'm a bit late for this very small PR, as I had to extend the expiration > date for my GPG signature key. > > Two small DT changes that have no functional impact. > > The following changes since commit

Re: [GIT PULL] ARM: at91: DT for 4.18

On Sat, May 26, 2018 at 12:50:33AM +0200, Alexandre Belloni wrote: > Arnd, Olof, > > I'm a bit late for this very small PR, as I had to extend the expiration > date for my GPG signature key. > > Two small DT changes that have no functional impact. > > The following changes since commit

Re: [PATCH v4 03/31] kconfig: reference environment variables directly and remove 'option env='

On Thu, May 24, 2018 at 6:45 AM, Masahiro Yamada wrote: > 2018-05-21 20:06 GMT+09:00 Ulf Magnusson : > >>> >>> static char *__expand_string(const char **str, bool (*is_end)(const char *)) >>> { >>> const char *in, *prev_in, *p; >>>

Re: [PATCH v2 6/7] platform/mellanox: Introduce support for Mellanox register access driver

On Sat, May 26, 2018 at 11:15:35AM +, Vadim Pasternak wrote: > > > > -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;

Re: [PATCH v2 6/7] platform/mellanox: Introduce support for Mellanox register access driver

On Sat, May 26, 2018 at 11:15:35AM +, Vadim Pasternak wrote: > > > > -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- > >

Re: [PATCH v4 03/31] kconfig: reference environment variables directly and remove 'option env='

On Thu, May 24, 2018 at 6:45 AM, Masahiro Yamada wrote: > 2018-05-21 20:06 GMT+09:00 Ulf Magnusson : > >>> >>> static char *__expand_string(const char **str, bool (*is_end)(const char *)) >>> { >>> const char *in, *prev_in, *p; >>> char *new, *out; >>> size_t outlen; >>>

[PATCH 2/3] Documentation: usb: add documentation for USB CCID Gadget Device

Signed-off-by: Marcus Folkesson --- Documentation/usb/gadget_ccid.rst | 267 ++ 1 file changed, 267 insertions(+) create mode 100644 Documentation/usb/gadget_ccid.rst diff --git a/Documentation/usb/gadget_ccid.rst

[PATCH 2/3] Documentation: usb: add documentation for USB CCID Gadget Device

Signed-off-by: Marcus Folkesson --- Documentation/usb/gadget_ccid.rst | 267 ++ 1 file changed, 267 insertions(+) create mode 100644 Documentation/usb/gadget_ccid.rst diff --git a/Documentation/usb/gadget_ccid.rst b/Documentation/usb/gadget_ccid.rst new

[PATCH 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

Signed-off-by: Marcus Folkesson --- drivers/usb/gadget/Kconfig | 17 + drivers/usb/gadget/function/Makefile | 1 + drivers/usb/gadget/function/f_ccid.c | 988 +++ drivers/usb/gadget/function/f_ccid.h | 91

[PATCH 3/3] MAINTAINERS: add USB CCID Gadget Device

Add MAINTAINERS entry for USB CCID Gadget Device Signed-off-by: Marcus Folkesson --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 078fd80f664f..e77c3d2bec89 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@

[PATCH 3/3] MAINTAINERS: add USB CCID Gadget Device

Add MAINTAINERS entry for USB CCID Gadget Device Signed-off-by: Marcus Folkesson --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 078fd80f664f..e77c3d2bec89 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -14541,6 +14541,14 @@ L:

[PATCH 1/3] usb: gadget: ccid: add support for USB CCID Gadget Device

Signed-off-by: Marcus Folkesson --- drivers/usb/gadget/Kconfig | 17 + drivers/usb/gadget/function/Makefile | 1 + drivers/usb/gadget/function/f_ccid.c | 988 +++ drivers/usb/gadget/function/f_ccid.h | 91 include/uapi/linux/usb/ccid.h|

Re: Bugs involving maliciously crafted file system

On Sat, May 26, 2018 at 07:12:49PM +0200, Dmitry Vyukov wrote: > > I don't see that "some kind of machine learning or expert system > evaluation" is feasible. At least not in short/mid-term. There are > innocently-looking bugs that actually turn out to be very bad, and > there are badly looking

Re: Bugs involving maliciously crafted file system

On Sat, May 26, 2018 at 07:12:49PM +0200, Dmitry Vyukov wrote: > > I don't see that "some kind of machine learning or expert system > evaluation" is feasible. At least not in short/mid-term. There are > innocently-looking bugs that actually turn out to be very bad, and > there are badly looking

[GIT pull] x86/pti updates for 4.17

Linus, please pull the latest x86-pti-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pti-for-linus Two fixes for the SSBD mitigation code: - Expose SSBD properly to guests. This got broken when the CPU feature flags got reshuffled. - Simplify

[GIT pull] x86/pti updates for 4.17

Linus, please pull the latest x86-pti-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pti-for-linus Two fixes for the SSBD mitigation code: - Expose SSBD properly to guests. This got broken when the CPU feature flags got reshuffled. - Simplify

[GIT pull] scheduler fixes for 4.17

Linus, please pull the latest sched-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-urgent-for-linus Three fixes for scheduler and kthread code: - Allow calling kthread_park() on an already parked thread - Restore the sched_pi_setprio()

[GIT pull] scheduler fixes for 4.17

Linus, please pull the latest sched-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-urgent-for-linus Three fixes for scheduler and kthread code: - Allow calling kthread_park() on an already parked thread - Restore the sched_pi_setprio()

[PATCH] parport: Add support for the WCH384 4S multi-IO card

This Multi-IO card has one serial 16550-like serial connectors. Here's the lspci output, after this commit is applied: 01:00.0 Serial controller [0700]: Device [1c00:3470] (rev 10) (prog-if 05 [16850]) Subsystem: Device [1c00:3470] Flags: fast devsel, IRQ 16 I/O ports at

[PATCH] parport: Add support for the WCH384 4S multi-IO card

This Multi-IO card has one serial 16550-like serial connectors. Here's the lspci output, after this commit is applied: 01:00.0 Serial controller [0700]: Device [1c00:3470] (rev 10) (prog-if 05 [16850]) Subsystem: Device [1c00:3470] Flags: fast devsel, IRQ 16 I/O ports at

Re: [PATCH 4/7] x86: remove a stray reference to pci-nommu.c

On Fri, 25 May 2018, Christoph Hellwig wrote: Subject should be: Documentation/x86: Remove . please > This is just the minimal workaround. The file file is mostly either stale file file? > and/or duplicative of Documentation/admin-guide/kernel-parameters.txt, > but that is much more work

Re: [PATCH 4/7] x86: remove a stray reference to pci-nommu.c

On Fri, 25 May 2018, Christoph Hellwig wrote: Subject should be: Documentation/x86: Remove . please > This is just the minimal workaround. The file file is mostly either stale file file? > and/or duplicative of Documentation/admin-guide/kernel-parameters.txt, > but that is much more work

Re: arch/powerpc/kernel/head_32.S:1106: Error: missing operand

On Sat, May 26, 2018 at 06:35:34AM +0200, Paul Menzel wrote: > Building the configuration created with `make tinyconfig` on the Power 8 > system IBM S822LC with Ubuntu 18.04 fails with the error below. > AS arch/powerpc/kernel/head_32.o > arch/powerpc/kernel/head_32.S: Assembler messages:

Re: arch/powerpc/kernel/head_32.S:1106: Error: missing operand

On Sat, May 26, 2018 at 06:35:34AM +0200, Paul Menzel wrote: > Building the configuration created with `make tinyconfig` on the Power 8 > system IBM S822LC with Ubuntu 18.04 fails with the error below. > AS arch/powerpc/kernel/head_32.o > arch/powerpc/kernel/head_32.S: Assembler messages:

Re: [PATCH v2] mm: fix race between kmem_cache destroy, create and deactivate

On Tue, May 22, 2018 at 01:13:36PM -0700, Shakeel Butt wrote: > The memcg kmem cache creation and deactivation (SLUB only) is > asynchronous. If a root kmem cache is destroyed whose memcg cache is in > the process of creation or deactivation, the kernel may crash. > > Example of one such crash: >

Re: [PATCH v2] mm: fix race between kmem_cache destroy, create and deactivate

On Tue, May 22, 2018 at 01:13:36PM -0700, Shakeel Butt wrote: > The memcg kmem cache creation and deactivation (SLUB only) is > asynchronous. If a root kmem cache is destroyed whose memcg cache is in > the process of creation or deactivation, the kernel may crash. > > Example of one such crash: >

Re: [PATCH] memcg: force charge kmem counter too

On Fri, May 25, 2018 at 11:55:01AM -0700, Shakeel Butt wrote: > Based on several conditions the kernel can decide to force charge an > allocation for a memcg i.e. overcharge memcg->memory and memcg->memsw > counters. Do the same for memcg->kmem counter too. In cgroup-v1, this > bug can cause a

Re: [PATCH] memcg: force charge kmem counter too

On Fri, May 25, 2018 at 11:55:01AM -0700, Shakeel Butt wrote: > Based on several conditions the kernel can decide to force charge an > allocation for a memcg i.e. overcharge memcg->memory and memcg->memsw > counters. Do the same for memcg->kmem counter too. In cgroup-v1, this > bug can cause a

Re: arch/powerpc/kernel/head_32.S:1106: Error: missing operand

Dear Christophe, Am 26.05.2018 um 18:02 schrieb christophe leroy: Le 26/05/2018 à 06:35, Paul Menzel a écrit : Building the configuration created with `make tinyconfig` on the Power 8 system IBM S822LC with Ubuntu 18.04 fails with the error below. ``` $ git describe --dirty

Re: arch/powerpc/kernel/head_32.S:1106: Error: missing operand

Dear Christophe, Am 26.05.2018 um 18:02 schrieb christophe leroy: Le 26/05/2018 à 06:35, Paul Menzel a écrit : Building the configuration created with `make tinyconfig` on the Power 8 system IBM S822LC with Ubuntu 18.04 fails with the error below. ``` $ git describe --dirty

Re: [PATCH 3/6] arm64: dts: hisilicon: Add missing cooling device properties for CPUs

Hi Viresh, On 2018/5/26 19:00, Wei Xu wrote: > Hi Viresh, > > On 2018/5/25 6:40, 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 for a

Re: [PATCH 3/6] arm64: dts: hisilicon: Add missing cooling device properties for CPUs

Hi Viresh, On 2018/5/26 19:00, Wei Xu wrote: > Hi Viresh, > > On 2018/5/25 6:40, 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 for a

Re: [PATCH 3/6] arm64: dts: hisilicon: Add missing cooling device properties for CPUs

Hi Viresh, On 2018/5/25 6:40, 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 for a subset of CPUs of > a cluster then things will start

Re: [PATCH 3/6] arm64: dts: hisilicon: Add missing cooling device properties for CPUs

Hi Viresh, On 2018/5/25 6:40, 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 for a subset of CPUs of > a cluster then things will start

  1   2   3   4   >