Rasmus Villemoes writes:
> If a watchdog driver tells the framework that the device is running,
> the framework takes care of feeding the watchdog until userspace opens
> the device. If the userspace application which is supposed to do that
> never comes up properly, the watchdog is fed
On 1/16/19 3:33 PM, Mel Gorman wrote:
>>> + break;
>>> + }
>>> +
>>> + /*
>>> +* If low PFNs are being found and discarded then
>>> +* limit the scan as fast searching is finding
>>> +
On Wed, Jan 16, 2019 at 11:23:33AM +0100, Johan Hovold wrote:
> Make sure to disable and deregister the switch on late probe errors to
> avoid use-after-free when the device-resource-managed switch is freed.
>
> Fixes: 14fceff4771e ("net: dsa: Add Lantiq / Intel DSA driver for vrx200")
> Cc:
Khalid Aziz writes:
> I am continuing to build on the work Juerg, Tycho and Julian have done
> on XPFO.
Awesome!
> A rogue process can launch a ret2dir attack only from a CPU that has
> dual mapping for its pages in physmap in its TLB. We can hence defer
> TLB flush on a CPU until a process
* Pavel Machek [190116 13:58]:
> Hi!
>
> > * Pavel Machek [181227 10:17]:
> > > Ok, I really need SMS messages, too.
> > >
> > > Fortunately, they are on /dev/motmdm9, in PDU format. Quite
> > > logical. And you probably need to acknowledge them, using PDU,
> > > too... (because otherwise
On Wed, Jan 16, 2019 at 2:22 AM Daniel Baluta wrote:
>
> On Tue, Jan 15, 2019 at 10:58 PM Rob Herring wrote:
> >
> > On Tue, Jan 08, 2019 at 01:05:51PM +, Viorel Suman wrote:
> > > Add the DT binding documentation for Audio Mixer
> > > machine driver.
> > >
> > > Signed-off-by: Viorel Suman
On Wed, 16 Jan 2019, Peter Zijlstra wrote:
> On Wed, Jan 16, 2019 at 12:50:42PM +, Valentin Schneider wrote:
> > Hi,
> >
> > I've been wandering around preempt_schedule_irq() in sched/core.c, and
> > got curious regarding how the arch code calls it.
> >
> > The main part of
On Tue, Jan 15, 2019 at 04:54:38PM -0800, Sean Christopherson wrote:
> On Tue, Jan 15, 2019 at 04:38:49PM -0600, Josh Poimboeuf wrote:
> > On Tue, Jan 15, 2019 at 11:06:17AM -0800, Sean Christopherson wrote:
> > > > I can see there are five options to solve it.
> > > >
> > > > 1) always inline
On Wed, Jan 16, 2019 at 09:47:41PM +0800, Dongli Zhang wrote:
> There is no need to wake up xen_blkif_schedule() as kthread_stop() is able
> to already wake up the kernel thread.
>
> Signed-off-by: Dongli Zhang
> ---
> drivers/block/xen-blkback/xenbus.c | 4 +---
> 1 file changed, 1
On Wed 16-01-19 13:37:22, Dmitry Vyukov wrote:
> On Wed, Jan 16, 2019 at 12:56 PM Jan Kara wrote:
> >
> > On Wed 16-01-19 12:03:27, Dmitry Vyukov wrote:
> > > On Wed, Jan 16, 2019 at 11:43 AM Jan Kara wrote:
> > > >
> > > > On Wed 16-01-19 10:47:56, Dmitry Vyukov wrote:
> > > > > On Fri, Jan 11,
Am 16.01.19 um 15:36 schrieb Jiri Pirko:
> Wed, Jan 16, 2019 at 03:25:02PM CET, starni...@g.ncu.edu.tw wrote:
>> Split LoRaWAN related skb definitions from lora/lorawan_netdev.h into
>> another header lora/lorawan_skb.h.
>
> What is the motivation for this change?
I suggested it because skbs
On Wed, Jan 16, 2019 at 03:34:55PM +1100, Dave Chinner wrote:
> On Tue, Jan 15, 2019 at 09:23:12PM -0500, Jerome Glisse wrote:
> > On Tue, Jan 15, 2019 at 06:01:09PM -0800, Dan Williams wrote:
> > > On Tue, Jan 15, 2019 at 5:56 PM Jerome Glisse wrote:
> > > > On Tue, Jan 15, 2019 at 04:44:41PM
> The actual error that we had from devm_gpiod_get_optional() was
> -EPROBE_DEFER, due to the GPIO being provided by a driver that is
> probed later than the Ethernet controller driver.
>
> To fix this, we simply add the missing device_del() invocation in the
> error path.
Hi Thomas
On Fri, 11 Jan 2019 14:29:28 +
Peter Rosin wrote:
> On 2019-01-10 20:25, Boris Brezillon wrote:
> > On Thu, 10 Jan 2019 18:51:21 +
> > Peter Rosin wrote:
> >
> >> On 2019-01-10 18:29, Boris Brezillon wrote:
> >>> On Thu, 10 Jan 2019 15:10:48 +
> >>> Peter Rosin wrote:
> >>>
On 16/01/2019 02:54, Martin K. Petersen wrote:
Hi John,
Hi Martin,
So in this case I think that accessor functions are actually better
because they allow us to print a big fat warning when you twiddle
something you shouldn't post-initialization. So that's something I think
we could--and
Wed, Jan 16, 2019 at 03:25:02PM CET, starni...@g.ncu.edu.tw wrote:
>Split LoRaWAN related skb definitions from lora/lorawan_netdev.h into
>another header lora/lorawan_skb.h.
What is the motivation for this change?
Wed, Jan 16, 2019 at 03:25:00PM CET, starni...@g.ncu.edu.tw wrote:
>Mention the LoRaWAN network feature to distinguish it from other
>Low-Power Wide-Area Network like Sigfox and NB-IoT.
>
>Signed-off-by: Jian-Hong Pan
>---
> net/lorawan/Kconfig | 3 ++-
> 1 file changed, 2 insertions(+), 1
Wed, Jan 16, 2019 at 03:24:58PM CET, starni...@g.ncu.edu.tw wrote:
>The net device may be missed to be put after error check. This patch
>fixes the issue to prevent the leakage.
>
>Signed-off-by: Jian-Hong Pan
>---
> net/lorawan/socket.c | 12
> 1 file changed, 4 insertions(+), 8
Wed, Jan 16, 2019 at 03:24:54PM CET, starni...@g.ncu.edu.tw wrote:
>Signed-off-by: Jian-Hong Pan
>---
Patches like this are in general frowned upon. Do one change in one
patch. Put some patch description.
Joerg,
On 1/16/19 8:26 PM, j...@8bytes.org wrote:
> How about the attached diff? If
> I understand the problem correctly, it should fix the problem more
> reliably.
>
> Thanks,
>
> Joerg
>
> diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
> index
Joerg,
On 1/16/19 8:03 PM, j...@8bytes.org wrote:
> Hi Suravee,
>
> On Wed, Jan 16, 2019 at 04:15:10AM +, Suthikulpanit, Suravee wrote:
>> From: Suravee Suthikulpanit
>>
>> When a device switches domain, IOMMU driver detach device from the old
>> domain, and attach device to the new domain.
On Mon, Jan 14, 2019 at 5:30 PM Masahiro Yamada
wrote:
>
> No one uses archmrproper.
>
> Signed-off-by: Masahiro Yamada
> ---
Applied to linux-kbuild/fixes.
>
> Makefile| 4 ++--
> arch/h8300/Makefile | 2 --
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git
On Tue, Jan 15, 2019 at 5:07 PM Masahiro Yamada
wrote:
>
> Commit c3ff2a5193fa ("powerpc/32: add stack protector support")
> caused kernel panic on PowerPC if an external module is used with
> CONFIG_STACKPROTECTOR because the 'prepare' target was not executed
> for the external module build.
>
>
On Wed, 16 Jan 2019 15:16:29 +0100
Andreas Ziegler wrote:
> When printing multiple uprobe arguments as strings the output for the
> earlier arguments would also include all later string arguments.
>
> This is best explained in an example:
>
> Consider adding a uprobe to a function receiving
On Sat, Jan 5, 2019 at 12:02 PM Masahiro Yamada
wrote:
>
> Remove the dot-prefixing since it is just a matter of the
> .gitignore file.
>
> Signed-off-by: Masahiro Yamada
> ---
Applied to linux-kbuild/fixes.
>
> scripts/kconfig/.gitignore | 1 +
> scripts/kconfig/Makefile | 36
On 16/01/2019 14:17, Boris Ostrovsky wrote:
> On Wed, Jan 16, 2019 at 08:50:13AM +0100, Juergen Gross wrote:
>
>> @@ -1650,13 +1650,14 @@ void xen_callback_vector(void)
>> xen_have_vector_callback = 0;
>> return;
>> }
>> -
On Wed, Jan 16, 2019 at 02:15:10PM +0100, Vlastimil Babka wrote:
> >
> > + if (free_pfn < high_pfn) {
> > + update_fast_start_pfn(cc, free_pfn);
> > +
> > + /*
> > +* Avoid if skipped recently. Move
> On Jan 16, 2019, at 6:22 AM, Arnaldo Carvalho de Melo wrote:
>
> Em Wed, Jan 16, 2019 at 02:12:37PM +, Song Liu escreveu:
>>
>>
>>> On Jan 16, 2019, at 6:00 AM, Arnaldo Carvalho de Melo
>>> wrote:
>>>
>>> Em Tue, Jan 15, 2019 at 04:14:06PM -0800, Song Liu escreveu:
This patch
On 16/01/2019 14:44, Mike Rapoport wrote:
> Add check for the return value of memblock_alloc*() functions and call
> panic() in case of error.
> The panic message repeats the one used by panicing memblock allocators with
> adjustment of parameters to include only relevant ones.
>
> The
On Wed, Jan 16, 2019 at 09:47:41PM +0800, Dongli Zhang wrote:
> There is no need to wake up xen_blkif_schedule() as kthread_stop() is able
> to already wake up the kernel thread.
>
> Signed-off-by: Dongli Zhang
Reviewed-by: Roger Pau Monné
kthread_stop waits for the thread to exit, so it must
Split LoRaWAN related skb definitions from lora/lorawan_netdev.h into
another header lora/lorawan_skb.h.
Signed-off-by: Jian-Hong Pan
---
include/linux/lora/lorawan_netdev.h | 20 -
include/linux/lora/lorawan_skb.h| 33 +
net/lorawan/socket.c
On 1/16/19 12:39 AM, Ming Lei wrote:
> On Tue, Jan 15, 2019 at 08:17:36PM -0700, Jens Axboe wrote:
>> On 1/15/19 8:13 PM, Ming Lei wrote:
>>> On Tue, Jan 15, 2019 at 07:55:39PM -0700, Jens Axboe wrote:
On 1/15/19 7:25 PM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next
Mention the LoRaWAN network feature to distinguish it from other
Low-Power Wide-Area Network like Sigfox and NB-IoT.
Signed-off-by: Jian-Hong Pan
---
net/lorawan/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/lorawan/Kconfig b/net/lorawan/Kconfig
index
Split LoRaWAN related skb definitions from lora/lorawan_netdev.h into
another header lora/lorawan_skb.h.
Signed-off-by: Jian-Hong Pan
---
include/linux/lora/lorawan_netdev.h | 20 -
include/linux/lora/lorawan_skb.h| 33 +
net/lorawan/socket.c
The net device may be missed to be put after error check. This patch
fixes the issue to prevent the leakage.
Signed-off-by: Jian-Hong Pan
---
net/lorawan/socket.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/net/lorawan/socket.c b/net/lorawan/socket.c
index
The lorawan module is an abastraction layer over the LoRaWAN soft and
hard MAC. It passes the original buffer to the real MAC layer. So,
this patch removes the lrw_dev_hard_header function.
Signed-off-by: Jian-Hong Pan
---
net/lorawan/socket.c | 12
1 file changed, 12
Signed-off-by: Jian-Hong Pan
---
include/linux/lora/lorawan_netdev.h | 5 ++--
net/lorawan/socket.c| 43 ++---
2 files changed, 22 insertions(+), 26 deletions(-)
diff --git a/include/linux/lora/lorawan_netdev.h
b/include/linux/lora/lorawan_netdev.h
So, I guess this is to do w/ the magic of merge commits, but it looks
like the hunk changing the crtc_ww_class got lost:
~/src/linux master git show --pretty=short
08295b3b5beec9aac0f7a9db86f0fc3792039da3
drivers/gpu/drm/drm_modeset_lock.c
commit 08295b3b5beec9aac0f7a9db86f0fc3792039da3
Hi,
On Wed, 2019-01-16 at 14:44 +0100, Thomas Petazzoni wrote:
> Well prior to your code, there was already a possibility for both
> ci->phy and ci->usb_phy to be valid. I don't think it's really useful
> to avoid the fallback when a generic PHY has already been found, it's
> confusing. If really
Em Wed, Jan 16, 2019 at 02:12:37PM +, Song Liu escreveu:
>
>
> > On Jan 16, 2019, at 6:00 AM, Arnaldo Carvalho de Melo
> > wrote:
> >
> > Em Tue, Jan 15, 2019 at 04:14:06PM -0800, Song Liu escreveu:
> >> This patch handles PERF_RECORD_KSYMBOL in perf record/report.
> >> Specifically, map
Jian-Hong Pan (5):
net: lorawan: Refine the coding style
net: lorawan: Remove unused lrw_dev_hard_header function
net; lorawan: Fix net device leakage
net: lorawan: Fulfill the help text of Kconfig
net: lorawan: Split skb definitions into another header
On Wed, Jan 16, 2019 at 02:47:16PM +0100, Christophe Leroy wrote:
> Le 16/01/2019 à 14:18, Matthew Wilcox a écrit :
> > I disagree with your objective. Making more code common is a great idea,
> > but this patch is too unambitious. We should be heading towards one or
> > two page table
Em Tue, Jan 15, 2019 at 04:14:08PM -0800, Song Liu escreveu:
> This patch synthesize PERF_RECORD_KSYMBOL and PERF_RECORD_BPF_EVENT for
> BPF programs loaded before perf-record. This is achieved by gathering
> information about all BPF programs via sys_bpf.
>
> Signed-off-by: Song Liu
> ---
>
When printing multiple uprobe arguments as strings the output for the
earlier arguments would also include all later string arguments.
This is best explained in an example:
Consider adding a uprobe to a function receiving two strings as
parameters which is at offset 0xa0 in strlib.so and we want
On Tue, Jan 15, 2019 at 02:20:19PM +0100, Christoph Hellwig wrote:
> On Tue, Jan 15, 2019 at 09:37:42AM +0100, Joerg Roedel wrote:
> > On Mon, Jan 14, 2019 at 01:20:45PM -0500, Michael S. Tsirkin wrote:
> > > Which would be fine especially if we can manage not to introduce a bunch
> > > of
On Mon, 14 Jan 2019, Christian Hohnstaedt wrote:
> These options apply to all regulators in this chip.
>
> ti,strict-supply-voltage-supervision:
> Set STRICT flag in CONFIG1
> ti,under-voltage-limit-microvolt:
> Select 2.75, 2.95, 3.25 or 3.35 V UVLO in CONFIG1
>
On 1/16/19 2:40 PM, Steven Rostedt wrote:
On Wed, 16 Jan 2019 10:41:12 +0100
Andreas Ziegler wrote:
When printing multiple uprobe arguments as strings the output for the
earlier arguments would also include all later string arguments.
This is best explained in an example:
Consider adding a
> On Jan 16, 2019, at 6:00 AM, Arnaldo Carvalho de Melo wrote:
>
> Em Tue, Jan 15, 2019 at 04:14:06PM -0800, Song Liu escreveu:
>> This patch handles PERF_RECORD_KSYMBOL in perf record/report.
>> Specifically, map and symbol are created for ksymbol register, and
>> removed for ksymbol
On 2019/1/11 14:34, Zhou Wang wrote:
> On 2019/1/11 14:08, Herbert Xu wrote:
>> On Sat, Dec 22, 2018 at 03:51:44PM +0800, Zhou Wang wrote:
>>>
>>> +static struct crypto_alg hisi_zip_zlib = {
>>> + .cra_name = "zlib-deflate",
>>> + .cra_flags =
On Wed, Jan 16, 2019 at 09:05:40AM -0500, Michael S. Tsirkin wrote:
> On Tue, Jan 15, 2019 at 02:22:57PM +0100, Joerg Roedel wrote:
> > + max_size = dma_max_mapping_size(>dev);
> > +
>
>
> Should this be limited to ACCESS_PLATFORM?
>
> I see no reason to limit this without as guest can
>
On 1/16/19 1:14 PM, Arnd Bergmann wrote:
> (sorry for the late reply, I just realized that I had never sent out the
> mail after Lee asked me for a review last year and I had drafted
> my reply).
Hi Arnd,
Many thanks for reviewing, no worries :-)
>
> On Wed, Dec 12, 2018 at 9:48 AM Fabrice
Joerg,
On 1/16/19 8:26 PM, j...@8bytes.org wrote:
> On Wed, Jan 16, 2019 at 04:16:25AM +, Suthikulpanit, Suravee wrote:
>> diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
>> index 525659b88ade..ab31ba75da1b 100644
>> --- a/drivers/iommu/amd_iommu.c
>> +++
On Tue, Jan 15, 2019 at 02:22:57PM +0100, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Segments can't be larger than the maximum DMA mapping size
> supported on the platform. Take that into account when
> setting the maximum segment size for a block device.
>
> Signed-off-by: Joerg Roedel
>
On Mon, Jan 14, 2019 at 07:36:14AM +0500, Ivan Mironov wrote:
> Existing code disables watchdog on NMI right before completely hanging
> the system.
>
> There are two problems here:
>
> * First, watchdog is expected to reset the system in a case of such
>failure, no matter what.
Enjoy!
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
ib-mfd-input-watchdog-v5.1
for you to fetch changes up to
Hi Marcel,
On 2019-01-04 14:41, Marcel Holtmann wrote:
Hi Balakrishna,
We will collect the ramdump of BT controller when hardware error
event
received before rebooting the HCI layer. Before restarting a
subsystem
or a process running on a subsystem, it is often required to request
either a
Em Tue, Jan 15, 2019 at 04:14:06PM -0800, Song Liu escreveu:
> This patch handles PERF_RECORD_KSYMBOL in perf record/report.
> Specifically, map and symbol are created for ksymbol register, and
> removed for ksymbol unregister.
>
> This patch also set perf_event_attr.ksymbol properly. The flag is
On Wed, Jan 16, 2019 at 05:39:02PM +0800, Min Guo wrote:
> Hi Bin,
>
> On Tue, 2019-01-15 at 14:38 -0600, Bin Liu wrote:
> > Hi Min,
> >
> > very close, thanks.
> > Below I tried to explain a further cleanup in musb_clearb/w() and
> > musb_get/set_toggle() implementation. Please let me know if
Hi!
> * Pavel Machek [181227 10:17]:
> > Ok, I really need SMS messages, too.
> >
> > Fortunately, they are on /dev/motmdm9, in PDU format. Quite
> > logical. And you probably need to acknowledge them, using PDU,
> > too... (because otherwise you'll just get the same SMS over and over
> > and
On Wed, Jan 16, 2019 at 2:51 PM Linus Walleij wrote:
>
> On Wed, Jan 16, 2019 at 11:25 AM Arnd Bergmann wrote:
> > On Mon, Jan 14, 2019 at 11:27 AM Ulf Hansson wrote:
> > >
> > > +Linus Walleij (recently made a cleanup of the mmc bounce buffering code).
>
> Nah it's not THAT bounce buffer.
>
>
On Wed, Jan 16, 2019 at 11:25 AM Arnd Bergmann wrote:
> On Mon, Jan 14, 2019 at 11:27 AM Ulf Hansson wrote:
> >
> > +Linus Walleij (recently made a cleanup of the mmc bounce buffering code).
Nah it's not THAT bounce buffer.
> Linus probably knows more here, but I have a vague recollection of
>
From: Christophe Leroy
Since only the virtual address of allocated blocks is used,
lets use functions returning directly virtual address.
Those functions have the advantage of also zeroing the block.
[ MR:
- updated error message in alloc_stack() to be more verbose
- convereted several
Hi!
> > > > I did a quick test in my config... and it did not break my old setup
> > > > -- voice calls still work when set up over USB and with manual mixer
> > > > setup. That was good surprise.
> > >
> > > OK good to hear. Using the n_gsm port instead of USB during idle
> > > has a major PM
The memblock_alloc_base_nid() is a oneliner wrapper for
memblock_alloc_range_nid() without any side effect.
Replace it's usage by the direct calls to memblock_alloc_range_nid().
Signed-off-by: Mike Rapoport
---
include/linux/memblock.h | 3 ---
mm/memblock.c| 15 ---
2
The memblock_alloc_base() function tries to allocate a memory up to the
limit specified by its max_addr parameter and panics if the allocation
fails. Replace its usage with memblock_phys_alloc_range() and make the
callers check the return value and panic in case of error.
Signed-off-by: Mike
These functions are not used outside memblock. Make them static.
Signed-off-by: Mike Rapoport
---
include/linux/memblock.h | 4
mm/memblock.c| 4 ++--
2 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/include/linux/memblock.h b/include/linux/memblock.h
index
On Wed, Jan 16, 2019 at 12:50:42PM +, Valentin Schneider wrote:
> Hi,
>
> I've been wandering around preempt_schedule_irq() in sched/core.c, and
> got curious regarding how the arch code calls it.
>
> The main part of preempt_schedule_irq() is:
>
> do {
> preempt_disable();
>
Add panic() calls if memblock_alloc*() returns NULL.
Most of the changes are simply addition of
if(!ptr)
panic();
statements after the calls to memblock_alloc*() variants.
Exceptions are create_mem_map_page_table() and ia64_log_init() that were
slightly refactored to
On Wed, 16 Jan 2019 09:00:00 +0100
Claudio wrote:
> Indeed the perf event interface would be awesome, if only it would support
> tracing all processes.
>
> Unfortunately for my use case, it can only trace one process on any cpus, or
> all processes on one (1) cpu.
>
> I guess for some kind
Le 16/01/2019 à 14:18, Matthew Wilcox a écrit :
On Wed, Jan 16, 2019 at 06:42:22PM +0530, Anshuman Khandual wrote:
On 01/16/2019 06:00 PM, Matthew Wilcox wrote:
On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote:
On Wed 16-01-19 11:51:32, Anshuman Khandual wrote:
All
There is no need to wake up xen_blkif_schedule() as kthread_stop() is able
to already wake up the kernel thread.
Signed-off-by: Dongli Zhang
---
drivers/block/xen-blkback/xenbus.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/block/xen-blkback/xenbus.c
Add check for the return value of memblock_alloc*() functions and call
panic() in case of error.
The panic message repeats the one used by panicing memblock allocators with
adjustment of parameters to include only relevant ones.
The replacement was mostly automated with semantic patches like the
Add panic() calls if memblock_alloc*() returns NULL.
Most of the changes are simply addition of
if(!ptr)
panic();
statements after the calls to memblock_alloc*() variants.
Exceptions are pcpu_populate_pte() and kernel_map_range() that were
slightly refactored to
Add panic() calls if memblock_alloc() returns NULL.
The panic() format duplicates the one used by memblock itself and in order
to avoid explosion with long parameters list replace open coded allocation
size calculations with a local variable.
Signed-off-by: Mike Rapoport
---
init/main.c | 26
memblock_alloc() already clears the allocated memory, no point in doing it
twice.
Signed-off-by: Mike Rapoport
---
arch/c6x/mm/init.c | 1 -
arch/h8300/mm/init.c| 1 -
arch/ia64/kernel/mca.c | 2 --
arch/m68k/mm/mcfmmu.c | 1 -
arch/microblaze/mm/init.c | 6 ++
As all the memblock allocation functions return NULL in case of error
rather than panic(), the duplicates with _nopanic suffix can be removed.
Signed-off-by: Mike Rapoport
---
arch/arc/kernel/unwind.c | 3 +--
arch/sh/mm/init.c | 2 +-
arch/x86/kernel/setup_percpu.c | 10
As all the memblock_alloc*() users are now checking the return value and
panic() in case of error, the panic() call can be removed from the core
memblock allocator, namely memblock_alloc_try_nid().
Signed-off-by: Mike Rapoport
---
mm/memblock.c | 15 +--
1 file changed, 5
Add panic() calls if memblock_alloc() returns NULL.
The panic() format duplicates the one used by memblock itself and in order
to avoid explosion with long parameters list replace open coded allocation
size calculations with a local variable.
Signed-off-by: Mike Rapoport
---
Add panic() calls if memblock_alloc() returns NULL.
The panic() format duplicates the one used by memblock itself and in order
to avoid explosion with long parameters list replace open coded allocation
size calculations with a local variable.
Signed-off-by: Mike Rapoport
---
mm/percpu.c | 73
The last parameter of memblock_alloc_from() is the lower limit for the
memory allocation. When it is 0, the call is equivalent to
memblock_alloc().
Signed-off-by: Mike Rapoport
---
arch/alpha/kernel/core_cia.c | 2 +-
arch/alpha/kernel/pci_iommu.c | 4 ++--
arch/alpha/kernel/setup.c | 2
Currently, memblock has several internal functions with overlapping
functionality. They all call memblock_find_in_range_node() to find free
memory and then reserve the allocated range and mark it with kmemleak.
However, there is difference in the allocation constraints and in fallback
strategies.
The __memblock_alloc_base() function tries to allocate a memory up to the
limit specified by its max_addr parameter. Depending on the value of this
parameter, the __memblock_alloc_base() can is replaced with the appropriate
memblock_phys_alloc*() variant.
Signed-off-by: Mike Rapoport
---
Make the memblock_phys_alloc() function an inline wrapper for
memblock_phys_alloc_range() and update the memblock_phys_alloc() callers to
check the returned value and panic in case of error.
Signed-off-by: Mike Rapoport
---
arch/arm/mm/init.c | 4
arch/arm64/mm/mmu.c
Rename memblock_alloc_range() to memblock_phys_alloc_range() to emphasize
that it returns a physical address.
While on it, remove the 'enum memblock_flags' parameter from this function
as its only user anyway sets it to MEMBLOCK_NONE, which is the default for
the most of memblock allocations.
The memblock_phys_alloc_try_nid() function tries to allocate memory from
the requested node and then falls back to allocation from any node in the
system. The memblock_alloc_base() fallback used by this function panics if
the allocation fails.
Replace the memblock_alloc_base() fallback with the
The calls to memblock_alloc_base(size, align, MEMBLOCK_ALLOC_ANYWHERE) and
memblock_phys_alloc(size, align) are equivalent as both try to allocate
'size' bytes with 'align' alignment anywhere in the memory and panic if hte
allocation fails.
The conversion is done using the following semantic
[ Cc'ing Masami as he maintains uprobes (we need to add uprobes to
the MAINTAINERS file ]
-- Steve
On Wed, 16 Jan 2019 13:20:27 +0200
Elena Reshetova wrote:
> atomic_t variables are currently used to implement reference
> counters with the following properties:
> - counter is initialized
The allocation of the page tables memory in openrics uses
memblock_phys_alloc() and then converts the returned physical address to
virtual one. Use memblock_alloc_raw() and add a panic() if the allocation
fails.
Signed-off-by: Mike Rapoport
---
arch/openrisc/mm/init.c | 5 -
1 file changed,
Hi,
Current memblock API is quite extensive and, which is more annoying,
duplicated. Except the low-level functions that allow searching for a free
memory region and marking it as reserved, memblock provides three (well,
two and a half) sets of functions to allocate memory. There are several
Hello,
On Wed, 16 Jan 2019 14:30:28 +0100, Paul Kocialkowski wrote:
> > Why is this conditional on the generic PHY lookup failing?
> >
> > Don't we simply want:
> >
> > ci->phy = devm_phy_get(dev->parent, "usb-phy");
> > ci->usb_phy = devm_usb_get_phy_by_phandle(dev->parent, "phys",
While debugging a DMA mapping leak, I needed to access
debug_dma_dump_mappings() but easily from user space.
This patch adds a /sys/kernel/debug/dma-api/dump file which contain all
current DMA mapping.
Signed-off-by: Corentin Labbe
---
kernel/dma/debug.c | 47
When building an allyesconfig build with Clang, the kernel fails to link
arch/x86/platform/efi/efi_64.o because of a failed BUILD_BUG_ON:
ld: arch/x86/platform/efi/efi_64.o: in function `efi_sync_low_kernel_mappings':
(.text+0x8e5): undefined reference to `__compiletime_assert_277'
Since there
ub.com/0day-ci/linux/commits/Camelia-Groza/net-phy-phy-driver-features-are-mandatory/20190116-004308
>
>
> in testcase: trinity
> with following parameters:
>
> runtime: 300s
>
> test-description: Trinity is a linux system call fuzz tester.
> test-url: http://code
16.01.2019 15:55, Joerg Roedel пишет:
> On Tue, Jan 15, 2019 at 07:33:54PM +0300, Dmitry Osipenko wrote:
>> Should I expect that the patches will appear in the IOMMU git and in
>> -next consequently? Please let me know if there is any problem with
>> the applying of the patches.
>
> Hmm, I
On Wed, 16 Jan 2019 10:41:12 +0100
Andreas Ziegler wrote:
> When printing multiple uprobe arguments as strings the output for the
> earlier arguments would also include all later string arguments.
>
> This is best explained in an example:
>
> Consider adding a uprobe to a function receiving
Hi Masami,
On Tue, Jan 15, 2019 at 03:23:39PM +0900, Masami Hiramatsu wrote:
> Hello,
>
> Here is the v2 series of update of the kprobe blacklist
> checking on arm64.
>
> I found that some blacklist checking code were mis-placed in
> arch_prepare_kprobe() and arch_within_kprobe_blacklist().
>
On Wed 16-01-19 18:57:13, Anshuman Khandual wrote:
>
>
> On 01/16/2019 06:14 PM, Michal Hocko wrote:
> > On Wed 16-01-19 04:30:18, Matthew Wilcox wrote:
> >> On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote:
> >>> On Wed 16-01-19 11:51:32, Anshuman Khandual wrote:
> All
Le 16/01/2019 à 14:16, Jonathan Neuschäfer a écrit :
On Wed, Jan 16, 2019 at 07:55:29AM +0100, Christophe Leroy wrote:
Le 16/01/2019 à 01:35, Jonathan Neuschäfer a écrit :
Thinning the kernel down a bit actually makes it boot again. Ooops...!
Maybe enabling CONFIG_STRICT_KERNEL_RWX has made
On Wed 16-01-19 05:18:27, Matthew Wilcox wrote:
> On Wed, Jan 16, 2019 at 06:42:22PM +0530, Anshuman Khandual wrote:
> > On 01/16/2019 06:00 PM, Matthew Wilcox wrote:
> > > On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote:
> > >> On Wed 16-01-19 11:51:32, Anshuman Khandual wrote:
> >
Hi,
On Wed, 2019-01-16 at 11:53 +0100, Thomas Petazzoni wrote:
> Hello,
>
> Thanks for the patch!
And thanks for the review!
> On Wed, 16 Jan 2019 11:10:51 +0100, Paul Kocialkowski wrote:
> > According to the chipidea driver bindings, the USB PHY is specified via
> > the "phys" phandle node.
801 - 900 of 1215 matches
Mail list logo
