Due to either a fast search of the free list or a linear scan, it's possible
for multiple compaction instances to pick the same pageblock for migration.
This is lucky for one scanner and increased scanning for all the others. It
also opens a race to allocate the resulting free block.
This patch
This patch fixes the SDMMC Controllers address space to be exact
defined register address range as per the design.
SDMMC Controller supporting Command Queue has CQHCI registers at
offset 0xF000.
This fix helps to identify the Tegra SDMMC Controllers supporting
Command Queue based on the size of
The migration scanner is a linear scan of a zone which is a potentially
very large search space. Furthermore, many pageblocks are unusable such
as those filled with reserved pages or partially filled with pages that
cannot migrate. These still get scanned in the common case of allocating
a THP and
On 12/14/18 2:47 PM, Frank Rowand wrote:
> On 12/14/18 9:15 AM, Rob Herring wrote:
>> On Fri, Dec 14, 2018 at 12:43 AM wrote:
>>>
>>> From: Frank Rowand
>>>
>>> The phandle cache contains struct device_node pointers. The refcount
>>> of the pointers was not incremented while in the cache,
On 2018-12-14 17:02, Paul Moore wrote:
> On Fri, Dec 14, 2018 at 11:27 AM Richard Guy Briggs wrote:
> > On 2018-12-12 08:03, Paul Moore wrote:
> > > On Fri, Nov 16, 2018 at 12:34 PM Richard Guy Briggs
> > > wrote:
> > > > On user and remote filesystems, a forced umount can still hang due to
> >
release_pages() is a simpler version of free_unref_page_list() but it
tracks the highest PFN for caching the restart point of the compaction
free scanner. This patch optionally tracks the highest PFN in the core
helper and converts compaction to use it.
Signed-off-by: Mel Gorman
---
The last_migrated_pfn field is a bit dubious as to whether it really helps
but either way, the information from it can be inferred without increasing
the size of compact_control so remove the field.
Signed-off-by: Mel Gorman
---
mm/compaction.c | 25 +
mm/internal.h |
When compaction is finishing, it uses a flag to ensure the pageblock is
complete. However, in general it makes sense to always complete migration
of a pageblock. Minimally, skip information is based on a pageblock and
partially scanned pageblocks may incur more scanning in the future. The
It's non-obvious that high-order free pages are split into order-0
pages from the function name. Fix it.
Signed-off-by: Mel Gorman
---
mm/compaction.c | 60 -
1 file changed, 29 insertions(+), 31 deletions(-)
diff --git a/mm/compaction.c
compact_control spans two cache lines with write-intensive lines on
both. Rearrange so the most write-intensive fields are in the same
cache line. This has a negligible impact on the overall performance of
compaction and is more a tidying exercise than anything.
Signed-off-by: Mel Gorman
---
When pageblocks get fragmented, watermarks are artifically boosted to pages
are reclaimed to avoid further fragmentation events. However, compaction
is often either fragmentation-neutral or moving movable pages away from
unmovable/reclaimable pages. As the actual watermarks are preserved,
allow
Reserved pages are set at boot time, tend to be clustered and almost
never become unreserved. When isolating pages for migrating, skip
the entire pageblock is one PageReserved page is encountered on the
grounds that it is highly probable the entire pageblock is reserved.
The impact depends on the
The isolate and migrate scanners should never isolate more than a pageblock
of pages so unsigned int is sufficient saving 8 bytes on a 64-bit build.
Signed-off-by: Mel Gorman
---
mm/internal.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/internal.h b/mm/internal.h
This is a very preliminary RFC. I'm posting this early as the
__GFP_THISNODE discussion continues and has started looking at the
compaction implementation and it'd be worth looking at this series
fdirst. The cc list is based on that dicussion just to make them aware
it exists. A v2 will have a
Pages with no migration handler use a fallback hander which sometimes
works and sometimes persistently fails such as blockdev pages. Migration
will retry a number of times on these persistent pages which is wasteful
during compaction. This patch will fail migration immediately unless the
caller is
Hi,
On Mon, Oct 15, 2018 at 3:39 PM Matthias Kaehlcke wrote:
>
> With commit e16337622016 ("Bluetooth: Handle bt_accept_enqueue() socket
> atomically") lock_sock[_nested]() is used to acquire the socket lock
> before manipulating the socket. lock_sock[_nested]() may block, which
> is problematic
On Fri, Dec 14, 2018 at 11:42:01PM +0100, Thomas Schöbel-Theuer wrote:
> Ah, I overlooked that commit e56c92565dfe2 is already providing a different
> solution to the same problem in newer kernels _only_, as a _side_ effect
> (not clear to me from the description, but clear from reading the code).
On Fri, Dec 14, 2018 at 12:38:15PM -0800, Todd Kjos wrote:
> 44d8047f1d8 ("binder: use standard functions to allocate fds")
> exposed a pre-existing issue in the binder driver.
>
> fdget() is used in ksys_ioctl() as a performance optimization.
> One of the rules associated with fdget() is that
$*)(
#*I backuped your phone\_
_-All photo, video, contacts and private record cams.$/
$@Read my offer in the attached PDF file(&
$/To track the reading of a message and the actions in it, I use the facebook
pixel^&
^!And at this moment I know that you have read through this email message*&
/_-^
Hi Cezary,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on spi/for-next]
[also build test WARNING on v4.20-rc6 next-20181214]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
On 12/14/18 9:15 AM, Rob Herring wrote:
> On Fri, Dec 14, 2018 at 12:43 AM wrote:
>>
>> From: Frank Rowand
>>
>> The phandle cache contains struct device_node pointers. The refcount
>> of the pointers was not incremented while in the cache, allowing use
>> after free error after kfree() of the
From: Arnd Bergmann
Date: Fri, 14 Dec 2018 23:22:10 +0100
> On Fri, Dec 14, 2018 at 10:23 PM David Miller wrote:
>>
>> From: Arnd Bergmann
>> Date: Mon, 10 Dec 2018 21:45:07 +0100
>>
>> > The get_mac_address() function is normally inline, but when it is
>> > not, we get a warning that this
On 12/14/18 22:27, Thomas Schoebel-Theuer wrote:
On 12/14/18 21:24, Borislav Petkov wrote:
Because apei_resources_fini() happens under the same condition check and
if arch_apei_filter_addr was false, it should not become true, all of a
sudden. Or?
please take a look at the stacktrace. For
On 12/14/18 1:56 PM, Michael Bringmann wrote:
> On 12/14/2018 11:20 AM, Rob Herring wrote:
>> On Fri, Dec 14, 2018 at 12:43 AM wrote:
>>>
>>> From: Frank Rowand
>>>
>>> Non-overlay dynamic devicetree node removal may leave the node in
>>> the phandle cache. Subsequent calls to
From: Mario Limonciello
Date: Tue, 11 Dec 2018 08:16:14 -0600
> All previous docks and dongles that have supported this feature use
> the RTL8153-AD chip.
>
> RTL8153-BND is a new chip that will be used in upcoming Dell type-C docks.
> It should be added to the whitelist of devices to activate
Commit 379d98ddf413 ("x86: vdso: Use $LD instead of $CC to link")
accidentally broke unwinding from userspace, because ld would strip the
.eh_frame sections when linking.
Originally, the compiler would implicitly add --eh-frame-hdr when
invoking the linker, but when this Makefile was converted
From: David Miller
Date: Fri, 14 Dec 2018 14:30:46 -0800 (PST)
> From: Salil Mehta
> Date: Tue, 11 Dec 2018 17:13:24 +
>
>> This patch-set adds few more debugfs commands to HNS3 Ethernet
>> Driver. Support has been added to query info related to below
>> items:
>> 1. Packet buffer
On 12/14/18 2:27 PM, Alistair Strachan wrote:
Commit 379d98ddf413 ("x86: vdso: Use $LD instead of $CC to link")
accidentally broke unwinding from userspace, because ld would strip the
.eh_frame sections when linking.
Originally, the compiler would implicitly add --eh-frame-hdr when
invoking the
HI James,
Thanks for the mail and comments, I will reply to you in the next mail.
2018-12-14 21:55 GMT+08:00, James Morse :
> Hi Dongjiu Geng,
>
> On 14/12/2018 10:15, Dongjiu Geng wrote:
>> When user space do memory recovery, it will check whether KVM and
>> guest support the error
From: Salil Mehta
Date: Tue, 11 Dec 2018 17:13:24 +
> This patch-set adds few more debugfs commands to HNS3 Ethernet
> Driver. Support has been added to query info related to below
> items:
> 1. Packet buffer descriptor ("echo bd info [queue no] [bd index] > cmd")
> 2. Manager table("echo
On 12/14/2018 10:49 PM, Stephen Boyd wrote:
> It seems that it may be possible to get to the regmap update call
> without ever initializing this variable, so just set it to 0 to be safe.
>
> Cc: Marek Vasut
> Cc: Alexey Firago
> Cc: Laurent Pinchart
> Cc: linux-renesas-...@vger.kernel.org
>
[Re: linux-next: Tree for Dec 14 (security/integrity/ima/)] On 14/12/2018 (Fri
15:26) Paul Gortmaker wrote:
> [Re: linux-next: Tree for Dec 14 (security/integrity/ima/)] On 14/12/2018
> (Fri 14:19) Mimi Zohar wrote:
>
> > On Fri, 2018-12-14 at 08:25 -0800, Randy Dunlap wrote:
> > >
> > > on
Commit 379d98ddf413 ("x86: vdso: Use $LD instead of $CC to link")
accidentally broke unwinding from userspace, because ld would strip the
.eh_frame sections when linking.
Originally, the compiler would implicitly add --eh-frame-hdr when
invoking the linker, but when this Makefile was converted
[+cc Lorenzo, Robin, Logan]
On Fri, Dec 14, 2018 at 04:33:19PM +, Sinan Kaya wrote:
> ACPI IORT table code relies on pci_request_acs() to be present. Define
> a stub function when CONFI_PCI is not set.
This doesn't seem like the simplest approach to me, but I probably
don't understand what's
Hi Laura,
On Fri, Dec 14, 2018 at 1:48 PM Laura Abbott wrote:
> Hi,
>
> There are two reports of a regression with unwinding with
> 379d98ddf413 ("x86: vdso: Use $LD instead of $CC to link")
>
> https://bugzilla.kernel.org/show_bug.cgi?id=201741
>
On Fri, Dec 14, 2018 at 10:27:25PM +0100, Thomas Schoebel-Theuer wrote:
> please take a look at the stacktrace. For some reason, and only at that
> specific hardware, the condition is false, there but later the indicated
> error exit is taken whose message you can see immediately before the stack
On Fri, Dec 14, 2018 at 10:23 PM David Miller wrote:
>
> From: Arnd Bergmann
> Date: Mon, 10 Dec 2018 21:45:07 +0100
>
> > The get_mac_address() function is normally inline, but when it is
> > not, we get a warning that this configuration is broken:
> >
> > WARNING: vmlinux.o(.text+0x4aff00):
In the linux-4.19 stable kernel, we get a warning about a type
mismatch between phys_addr_t and dma_addr_t:
drivers/gpu/drm/msm/disp/dpu1/dpu_dbg.c: In function
'_dpu_dbg_dump_dpu_dbg_bus':
drivers/gpu/drm/msm/disp/dpu1/dpu_dbg.c:2003:16: error: passing argument 3 of
'dma_alloc_coherent' from
Upstream commit 972910948fb6 ("ARM: dts: qcom: Remove Arrow SD600
eval board") removed this file because there are no known users,
but in linux-4.19.y, we still get a compile-time warnign for it:
arch/arm/boot/dts/qcom-apq8064-arrow-sd-600eval.dtb: Warning (graph_endpoint):
Commit 2e6ae11dd0d1c37f44cec51a58fb2092e55ed0f5 upstream.
qcom_slim_ngd_runtime_suspend is protected by an #ifdef,
qcom_slim_ngd_runtime_idle is now, which causes a build time warning:
drivers/slimbus/qcom-ngd-ctrl.c:1470:12: error: 'qcom_slim_ngd_runtime_idle'
defined but not used
Upstream commit 3e9efc3299dd ("i2c: aspeed: Handle master/slave combined irq
events
properly") reworked the interrupt handling and fixed a warning in the process:
drivers/i2c/busses/i2c-aspeed.c: In function 'aspeed_i2c_bus_irq':
drivers/i2c/busses/i2c-aspeed.c:567:1: error: label 'out' defined
From: Lubomir Rintel
Commit 33f49571d75024b1044cd02689ad2bdb4924cc80 upstream.
WARNING: unmet direct dependencies detected for BACKLIGHT_CLASS_DEVICE
Depends on [n]: HAS_IOMEM [=y] && BACKLIGHT_LCD_SUPPORT [=n]
Selected by [y]:
- FB_OLPC_DCON [=y] && STAGING [=y] && X86 [=y] &&
From: Vincent Guittot
Commit 11d4afd4ff667f9b6178ee8c142c36cb78bd84db upstream.
Create a config for enabling irq load tracking in the scheduler.
irq load tracking is useful only when irq or paravirtual time is
accounted but it's only possible with SMP for now.
Also use __maybe_unused to remove
Hi Greg,
I did some randconfig testing on linux-4.19 arm/arm64/x86. So far I needed
27 patches, most of which are also still needed in mainline Linux. I
had submitted some before, and others were not submitted previously
for some reason. I'll try to get those fixed in mainline and then
make sure
Commit 0eeec01488da9b1403c8c29e73eacac8af9e4bf2 upstream.
I ran into a new warning on randconfig kernels:
drivers/scsi/raid_class.c: In function 'raid_match':
drivers/scsi/raid_class.c:64:24: error: unused variable 'i'
[-Werror=unused-variable]
This looks like a very old problem that for some
Quoting Anson Huang (2018-12-07 02:03:34)
> i.MX7ULP has a Cortex-A7 CPU which can run in RUN mode
> or HSRUN mode, it is controlled in SMC1 module. The RUN
> mode and HSRUN mode will use different clock source for
> ARM, "divcore" for RUN mode and "hsrun_divcore" for HSRUN
> mode, so the control
Quoting Anson Huang (2018-12-07 02:03:29)
> There are HSRUN mode clock mux and divider in SCG1 module,
> and SMC1 can control i.MX7ULP CPU to run in RUN mode or
> HSRUN mode, the mode switch bits are actually a clock mux,
> add these clocks for clock driver and dtb to use.
>
> Signed-off-by:
On 12/14/2018 04:51 PM, Josh Poimboeuf wrote:
> On Fri, Dec 14, 2018 at 04:34:23PM -0500, Joe Lawrence wrote:
>> BTW, Petr/Miroslav/Josh, should we be annotating the selftests in
>> similar fashion?
>
> Probably so.
>
Just to clarify for Nicholas, the self-tests we're referring to are part
of
On Fri, Dec 14, 2018 at 8:48 PM Andreas Klinger
wrote:> Document properties reg and interrupts for OMAP GPIO
controller bindings
>
> Also add unit address in node name of the example
>
> Signed-off-by: Andreas Klinger
Acked-by: Linus Walleij
Yours,
Linus Walleij
On Sat, Dec 15, 2018 at 02:11:01AM +0530, Jagan Teki wrote:
> Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
>
> Add panel driver for it.
>
> Signed-off-by: Jagan Teki
> ---
> Changes for v2:
> - use simple structure for command init
> - update proper comments on power, reset
On Fri, Dec 14, 2018 at 11:27 AM Richard Guy Briggs wrote:
> On 2018-12-12 08:03, Paul Moore wrote:
> > On Fri, Nov 16, 2018 at 12:34 PM Richard Guy Briggs wrote:
> > > On user and remote filesystems, a forced umount can still hang due to
> > > attemting to fetch the fcaps of a mounted
Quoting Weiyi Lu (2018-12-09 23:32:31)
> diff --git a/drivers/clk/mediatek/clk-pll.c b/drivers/clk/mediatek/clk-pll.c
> index f0ff5f535c7e..81400601f107 100644
> --- a/drivers/clk/mediatek/clk-pll.c
> +++ b/drivers/clk/mediatek/clk-pll.c
> @@ -69,11 +71,13 @@ static unsigned long
Quoting Weiyi Lu (2018-12-09 23:32:40)
> From: James Liao
>
> Some modules may need to change its clock rate before turn on it.
> So changing PLL's rate when it is off should be allowed.
> This patch removes PLL enabled check before set rate, so that
> PLLs can set new frequency even if they are
Quoting Weiyi Lu (2018-12-09 23:32:36)
> + "apll2_ck"
> +};
> +
> +static const struct mtk_mux top_muxes[] = {
> + /* CLK_CFG_0 */
> + MUX_GATE_CLR_SET_UPD_FLAGS(CLK_TOP_MUX_AXI, "axi_sel",
> + axi_parents, 0x40,
> + 0x44, 0x48, 0, 2, 7, 0x004, 0,
__vdso_sgx_enter_enclave() gets another rewrite, this time to strip
it down to the bare minimum and explicitly break compliance with the
x86-64 ABI. Feedback from v4 revealed that __vdso_sgx_enter_enclave()
would need to save (a lot) more than just the non-volatile GPRs to be
compliant with the
On 12/12/2018 08:57 PM, Michael Ellerman wrote:
> Frank Rowand writes:
>> On 12/11/18 8:07 AM, Rob Herring wrote:
>>> On Tue, Dec 11, 2018 at 7:29 AM Michael Ellerman
>>> wrote:
> ...
diff --git a/drivers/of/base.c b/drivers/of/base.c
index 09692c9b32a7..d8e4534c0686 100644
---
On Fri, Dec 14, 2018 at 11:45:00AM -0800, Matthew Wilcox wrote:
> On Fri, Dec 14, 2018 at 11:40:45AM -0800, Joe Perches wrote:
> > On Fri, 2018-12-14 at 10:13 -0800, Matthew Wilcox wrote:
> > > On Fri, Dec 14, 2018 at 10:07:18AM -0800, Roman Gushchin wrote:
> > > > +/*
> > > > + * Allocate a
...to prepare for vDSO exception fixup, which will expose the error
code to userspace and runs before set_signal_archinfo(), i.e. squashes
the signal when fixup is successful.
Signed-off-by: Sean Christopherson
---
arch/x86/mm/fault.c | 26 ++
1 file changed, 14
syzbot has found a reproducer for the following crash on:
HEAD commit:eb6cf9f8cb9d Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11a09b6d40
kernel config:
Call fixup_vdso_exception() in all trap flows that generate signals to
userspace immediately prior to generating any such signal. If the
exception is fixed, return cleanly and do not generate a signal.
The goal of vDSO fixup is not to fixup all faults, nor is it to avoid
all signals, but rather
Quoting Weiyi Lu (2018-12-09 23:32:33)
> This patch adds the binding documentation for apmixedsys, audiosys,
> camsys, imgsys, infracfg, mcucfg, mfgcfg, mmsys, topckgen, vdecsys,
> vencsys and ipu for Mediatek MT8183.
>
> Signed-off-by: Weiyi Lu
> Reviewed-by: Rob Herring
> ---
Acked-by:
Intel Software Guard Extensions (SGX) SGX introduces a new CPL3-only
enclave mode that runs as a sort of black box shared object that is
hosted by an untrusted normal CPL3 process.
Enclave transitions have semantics that are a lovely blend of SYCALL,
SYSRET and VM-Exit. In a non-faulting
Why is "fixup" in the subject of this patch?
Quoting Weiyi Lu (2018-12-09 23:32:29)
> From: Owen Chen
>
> PLLs with tuner_en bit, such as APLL1, need to disable
> tuner_en before apply new frequency settings, or the new frequency
> settings (pcw) will not be applied.
> The tuner_en bit will be
Call fixup_sgx_enclu_exception() in the SIGSEGV and SIGBUS paths of
the page fault handler immediately prior to signaling. If the fault
is fixed, return cleanly and do not generate a signal.
In the SIGSEGV flow, make sure the error code passed to userspace has
been sanitized.
Suggested-by: Andy
The basic concept and implementation is very similar to the kernel's
exception fixup mechanism. The key differences are that the kernel
handler is hardcoded and the fixup entry addresses are relative to
the overall table as opposed to individual entries.
Hardcoding the kernel handler avoids the
On 12/14/2018 11:20 AM, Rob Herring wrote:
> On Fri, Dec 14, 2018 at 12:43 AM wrote:
>>
>> From: Frank Rowand
>>
>> Non-overlay dynamic devicetree node removal may leave the node in
>> the phandle cache. Subsequent calls to of_find_node_by_phandle()
>> will incorrectly find the stale entry.
On Thu, Dec 13, 2018 at 2:39 AM Sebastian Reichel
wrote:
> This migrates isp1704 driver from old GPIO API to new descriptor
> based GPIO API and drops useless platform data as a side-effect.
>
> Migration is simple, since all mainline users are DT based and
> DT API does not change. Out of tree
The current dentry number tracking code doesn't distinguish between
positive & negative dentries. It just reports the total number of
dentries in the LRU lists.
As excessive number of negative dentries can have an impact on system
performance, it will be wise to track the number of positive and
The nr_dentry_unused per-cpu counter tracks dentries in both the
LRU lists and the shrink lists where the DCACHE_LRU_LIST bit is set.
The shrink_dcache_sb() function moves dentries from the LRU list to a
shrink list and subtracts the dentry count from nr_dentry_unused. This
is incorrect as the
The list_lru structure is essentially just a pointer to a table of
per-node LRU lists. Even if CONFIG_MEMCG_KMEM is defined, the list
field is just used for LRU list registration and shrinker_id is set
at initialization. Those fields won't need to be touched that often.
So there is no point to
Quoting Rob Herring (2018-12-05 11:50:21)
> Convert string compares of DT node names to use of_node_name_eq helper
> instead. This removes direct access to the node name pointer.
>
> For instances using of_node_cmp, this has the side effect of now using
> case sensitive comparisons. This should
v3->v4:
- Drop patch 4 as it is just a minor optimization.
- Add a cc:stable tag to patch 1.
- Clean up some comments in patch 3.
v2->v3:
- With confirmation that the dummy array in dentry_stat structure
was never a replacement of a previously used field, patch 3 is now
reverted
On Fri, Dec 14, 2018 at 04:33:16PM +, Sinan Kaya wrote:
> We are compiling PCI code today for systems with ACPI and no PCI
> device present. Remove the useless code and reduce the tight
> dependency.
>
> Signed-off-by: Sinan Kaya
Acked-by: Bjorn Helgaas# PCI parts
Looks like most of
On Fri, Dec 14, 2018 at 04:34:23PM -0500, Joe Lawrence wrote:
> On 12/14/2018 11:56 AM, Nicholas Mc Guire wrote:
> > Sparse reported warnings about non-static symbols. For the variables a
> > simple static attribute is fine - for those symbols referenced by
> > livepatch via klp_func the
It seems that it may be possible to get to the regmap update call
without ever initializing this variable, so just set it to 0 to be safe.
Cc: Marek Vasut
Cc: Alexey Firago
Cc: Laurent Pinchart
Cc: linux-renesas-...@vger.kernel.org
Signed-off-by: Stephen Boyd
---
Hi,
There are two reports of a regression with unwinding with
379d98ddf413 ("x86: vdso: Use $LD instead of $CC to link")
https://bugzilla.kernel.org/show_bug.cgi?id=201741
https://bugzilla.redhat.com/show_bug.cgi?id=1659295
It looks like the unwinding information has been
stripped out. Any
On 2018-12-13 13:00, sh...@kernel.org wrote:
> From: Shuah Khan
>
> Commit b2d35fa5fc80 ("selftests: add headers_install to lib.mk") added
> khdr target to run headers_install target from the main Makefile. The
> logic uses KSFT_KHDR_INSTALL and top_srcdir as controls to initialize
> variables
Hi Zengtao,
On 12/14/2018 3:24 AM, Felipe Balbi wrote:
> Hi,
>
> "Zengtao (B)" writes:
>>> -Original Message-
>>> From: Felipe Balbi [mailto:ba...@kernel.org]
>>> Sent: Friday, December 14, 2018 4:52 PM
>>> To: Zengtao (B)
>>> Cc: liangshengjun ; Zengtao (B)
>>> ; Greg Kroah-Hartman
>>>
Quoting Jeffrey Hugo (2018-12-13 09:09:09)
> gcc_lpass_trig_clk is not used downstream, therefore there is no reason to
> expect it to be needed for clients. Let's remove it because messing with
> the clock has been observed to cause Linux hangs when the qdss_clk is
> initialized by rpmcc.
>
>
On 12/14/18 22:24, Andy Lutomirski wrote:
I should clarify again: I am not suggesting that we drop 32-bit
support in the forseeable future. (Well, I might eventually suggest
that we drop support for 32-bit *hardware* at some point, but not for
32-bit compat software.) Linux's compat code is
On Fri, 14 Dec 2018, Paul E. McKenney wrote:
> I would say that sys_membarrier() has zero-sized read-side critical
> sections, either comprising a single instruction (as is the case for
> synchronize_sched(), actually), preempt-disable regions of code
> (which are irrelevant to userspace
: x86_64_defconfig + FTRACE=y
> FUNCTION_TRACER=y, EXPERT=y, LATENCYTOP=y, SAMPLES=y,
> SAMPLE_LIVEPATCH=y
>
> Patch is against 4.20-rc6 (localversion-next is next-20181214)
> on top of 0001-livepatch-fix-non-static-warnings.patch
>
> samples/livepatch/livepatch-shadow-fix1.
From: Wen Yang
Date: Tue, 11 Dec 2018 12:20:46 +0800
> The driver was checking for non-NULL address.
> - adapter->napi[i]
>
> This is pointless as these will be always non-NULL, since the
> 'dapter->napi' is allocated in init_napi().
> It is safe to get rid of useless checks for addresses to
On 12/14/18 10:04 PM, David Rientjes wrote:
> On Wed, 12 Dec 2018, Vlastimil Babka wrote:
...
> Reclaim likely could be deterministically useful if we consider a redesign
> of how migration sources and targets are determined in compaction.
>
> Has anybody tried a migration scanner that isn't
From: Nathan Chancellor
Date: Mon, 10 Dec 2018 21:20:30 -0700
> Clang warns:
>
> drivers/net/ethernet/apm/xgene/xgene_enet_main.c:33:36: warning:
> tentative array definition assumed to have one element
> static const struct acpi_device_id xgene_enet_acpi_match[];
>
atch_shadow_fix2/enabled
>echo 0 > /sys/kernel/livepatch/livepatch_shadow_fix1/enabled
>rmmod livepatch-shadow-fix2
>rmmod livepatch-shadow-fix1
>rmmod livepatch-shadow-mod
> and dmesg output checked.
>
> Patch is against 4.20-rc6 (localversion-next is next-201812
Looks good to me
Thanks Christoph
Acked-by: Jon Derrick
On Fri, 2018-12-14 at 15:17 -0600, Bjorn Helgaas wrote:
> Conventional spelling in subject is
>
> PCI: vmd: Use dma_* APIs instead of direct method calls
>
> On Fri, Dec 07, 2018 at 11:07:19AM -0800, Christoph Hellwig wrote:
> > With
On Fri, Dec 14, 2018 at 09:26:18AM +0300, Dan Carpenter wrote:
> On Thu, Dec 13, 2018 at 03:01:46PM -0700, Jeremy Fertic wrote:
> > On Wed, Dec 12, 2018 at 11:23:16AM +0300, Dan Carpenter wrote:
> > > On Tue, Dec 11, 2018 at 05:54:56PM -0700, Jeremy Fertic wrote:
> > > > @@ -651,10 +649,12 @@
On Fri, Dec 14, 2018 at 12:13 PM Linus Torvalds
wrote:
>
> On Fri, Dec 14, 2018 at 10:58 AM Andy Lutomirski wrote:
> >
> > Does anyone know *why* Linux’s x32 has __kernel_long_t defined as long long?
>
> It *needs* to be long long, since the headers are used for builds in
> user mode using
On 12/14/18 21:24, Borislav Petkov wrote:
Because apei_resources_fini() happens under the same condition check and
if arch_apei_filter_addr was false, it should not become true, all of a
sudden. Or?
Hi Borislav,
please take a look at the stacktrace. For some reason, and only at that
From: Arnd Bergmann
Date: Mon, 10 Dec 2018 22:52:56 +0100
> ppp and hamradio have copies of the same code that uses a semaphore
> in place of a completion for historic reasons. Make it use the
> proper interface instead in all copies.
>
> Signed-off-by: Arnd Bergmann
Applied, thanks.
From: Arnd Bergmann
Date: Mon, 10 Dec 2018 22:17:20 +0100
> @@ -635,8 +636,9 @@ static int threadfunc(void *data)
> int i, step, err = 0, insert_retries = 0;
> struct thread_data *tdata = data;
>
> - up(_sem);
> - if (down_interruptible(_sem))
> + if
On Fri, Dec 14, 2018 at 1:22 PM Thomas Schöbel-Theuer
wrote:
>
> On 12/11/18 02:23, Andy Lutomirski wrote:
> > I'm seriously considering sending a patch to remove x32 support from
> > upstream Linux.
>
> I am downstream maintainer of several self-patched kernels at 1&1 Ionos.
> The kernels are
On Mon, 3 Dec 2018 12:08:47 -0800 Mike Kravetz wrote:
> These patches are a follow up to the RFC,
> http://lkml.kernel.org/r/20181024045053.1467-1-mike.krav...@oracle.com
> Comments made by Naoya were addressed.
>
> There are two primary issues addressed here:
> 1) For shared pmds, huge PE
On 12/11/18 02:23, Andy Lutomirski wrote:
I'm seriously considering sending a patch to remove x32 support from
upstream Linux.
I am downstream maintainer of several self-patched kernels at 1&1 Ionos.
The kernels are rolled out to several tenthousands of production servers
running in several
From: Arnd Bergmann
Date: Mon, 10 Dec 2018 21:45:07 +0100
> The get_mac_address() function is normally inline, but when it is
> not, we get a warning that this configuration is broken:
>
> WARNING: vmlinux.o(.text+0x4aff00): Section mismatch in reference from the
> function
From: Arnd Bergmann
Date: Mon, 10 Dec 2018 21:44:34 +0100
> We now get a link failure when CONFIG_INET is disabled, since
> tcp_gro_complete is unavailable:
>
> drivers/net/ethernet/hisilicon/hns3/hns3_enet.o: In function
> `hns3_set_gro_param':
> hns3_enet.c:(.text+0x230c): undefined
Conventional spelling in subject is
PCI: vmd: Use dma_* APIs instead of direct method calls
On Fri, Dec 07, 2018 at 11:07:19AM -0800, Christoph Hellwig wrote:
> With the bypass support for the direct mapping we might not always have
> methods to call, so use the proper APIs instead. The only
On Fri, Dec 07, 2018 at 11:07:18AM -0800, Christoph Hellwig wrote:
> From: Robin Murphy
>
> Rather than checking the DMA attribute at each callsite, just pass it
> through for acpi_dma_configure() to handle directly. That can then deal
> with the relatively exceptional DEV_DMA_NOT_SUPPORTED case
Flags field will be used in further commits (e.g. for keeping
SC_COMP_PROT), so let's bring those back. This commit effectively
reverts commit 1998b5ed9c9b ("l2tp: drop ->flags from struct
pppol2tp_session"), with some cosmetic changes.
Signed-off-by: Sam Protsenko
---
net/l2tp/l2tp_ppp.c | 52
101 - 200 of 1344 matches
Mail list logo
