On Sun, 2018-10-21 at 05:22 -0700, Metztli Information Technology
wrote:
> Niltze, all-
>
> Ever since I build reiser4 -patched [1] Linux kernel 4.18.xy
> iterations I have had kernel hanging issues --which manifest
> themselves after considerable load and/or multitasking in my local
> development
Announcing a new -ck release, 4.18-ck1 with the latest version of the
Multiple Queue Skiplist Scheduler, version 0.173. These are patches designed
to improve system responsiveness and interactivity with specific emphasis on
the desktop, but configurable for any workload.
linux-4.18-ck1:
-ck1
Linus Torvalds (2):
init: rename and re-order boot_cpu_state_init()
Linux 4.18
Martin KaFai Lau (1):
bpf: btf: Change tools/lib/bpf/btf to LGPL
Minchan Kim (1):
zram: remove BD_CAP_SYNCHRONOUS_IO with writeback feature
Ondrej Mosnacek (1):
crypto: x86/aegis,m
> -Original Message-
> From: David Binderman
> Sent: Monday, August 6, 2018 1:08 AM
> To: KY Srinivasan ; Haiyang Zhang
> ; Stephen Hemminger
> ; de...@linuxdriverproject.org; linux-
> ker...@vger.kernel.org
> Subject: linux-4.18-rc8/tools/hv/hv_kvp_daemo
ia64: mark special ia64 memory areas anonymous
squashfs metadata 2: electric boogaloo
mm: do not initialize TLB stack vma's with vma_init()
squashfs: more metadata hardening
Partially revert "block: fail op_is_write() requests to
read-only partitions"
On Wed, Aug 1, 2018 at 2:55 PM, Hugh Dickins wrote:
> On Wed, 1 Aug 2018, Kirill A. Shutemov wrote:
>> On Wed, Aug 01, 2018 at 11:31:52AM -0700, Hugh Dickins wrote:
>> > On Wed, 1 Aug 2018, Linus Torvalds wrote:
>> > >
>> > > Anyway, the upshot of all this is that I think I know what the ia64
>> >
On Wed, 1 Aug 2018 at 22:45, Linus Torvalds
wrote:
>
> I'd like to get this sorted out asap, although at this point I still
> think that I'll have to do an rc8 even though I feel like we may have
> caught everything.
No AOSP regressions in my limited smoke testing so far with
current HEAD: 6b4703
On Wed, 1 Aug 2018, Kirill A. Shutemov wrote:
> On Wed, Aug 01, 2018 at 11:31:52AM -0700, Hugh Dickins wrote:
> > On Wed, 1 Aug 2018, Linus Torvalds wrote:
> > >
> > > Anyway, the upshot of all this is that I think I know what the ia64
> > > problem was, and John sent the patch for the ashmem case
On Wed, Aug 01, 2018 at 01:56:19PM -0700, Linus Torvalds wrote:
> On Wed, Aug 1, 2018 at 1:52 PM Kirill A. Shutemov
> wrote:
> >
> > Is there a reason why we pass vma to flush_tlb_range?
>
> Yes. It's even in that patch.
>
> The fact is, real MM users *have* a vma, and passing it in to the TLB
On Wed, Aug 01, 2018 at 11:31:52AM -0700, Hugh Dickins wrote:
> On Wed, 1 Aug 2018, Linus Torvalds wrote:
> >
> > Anyway, the upshot of all this is that I think I know what the ia64
> > problem was, and John sent the patch for the ashmem case, and I'm
> > going to hold off reverting that vma_is_an
On Wed, Aug 1, 2018 at 1:52 PM Kirill A. Shutemov wrote:
>
> Is there a reason why we pass vma to flush_tlb_range?
Yes. It's even in that patch.
The fact is, real MM users *have* a vma, and passing it in to the TLB
flushing is the right thing to do. That allows architectures that care
(mainly po
On Wed, Aug 01, 2018 at 01:05:48PM -0700, Linus Torvalds wrote:
> On Wed, Aug 1, 2018 at 10:15 AM Linus Torvalds
> wrote:
> >
> > I'm still unhappy about the vma_init() ones, and I have not decided
> > how to go with those. Either the memset() in vma_init(), or just
> > reverting the (imho unneces
On Wed, Aug 1, 2018 at 10:15 AM Linus Torvalds
wrote:
>
> I'm still unhappy about the vma_init() ones, and I have not decided
> how to go with those. Either the memset() in vma_init(), or just
> reverting the (imho unnecessary) commit 2c4541e24c55. Kirill, Andrew,
> comments?
Ugh. Adding a memset
On Wed, Aug 01, 2018 at 10:15:05AM -0700, Linus Torvalds wrote:
> Tony, can you please double-check my commit ebad825cdd4e ("ia64: mark
> special ia64 memory areas anonymous") fixes things for you? I didn't
> even compile it, but it really looks so obvious that I just committed
> it directly. It's
On Wed, 1 Aug 2018, Linus Torvalds wrote:
>
> Anyway, the upshot of all this is that I think I know what the ia64
> problem was, and John sent the patch for the ashmem case, and I'm
> going to hold off reverting that vma_is_anonymous() false-positives
> commit after all.
I'd better send deletion
On Tue, Jul 31, 2018 at 10:43 AM Luck, Tony wrote:
>
> On Tue, Jul 31, 2018 at 08:03:28PM +0300, Kirill A. Shutemov wrote:
> > But it's not the only issue unfortunately. Tony reported issue with
> > booting ia64 with the patch. I have no clue why. I rechecked everything
> > ia64-specific and looks
On Tue, 31 Jul 2018, Kirill A. Shutemov wrote:
> On Tue, Jul 31, 2018 at 09:29:27AM +0300, Kirill A. Shutemov wrote:
> > On Mon, Jul 30, 2018 at 06:01:26PM -0700, Linus Torvalds wrote:
> > >
> > > So to me it looks like a historical check that simply doesn't
> > > "normally" trigger, but there's n
my x86 report
isPrevious: true
Build:
Android-x86/android_x86/x86:8.1.0/OPM6.171019.030.B1/cwhuang0618:userdebug/test-keys
Hardware: unknown
Revision: 0
Bootloader: unknown
Radio: unknown
Kernel: Linux version 4.18.0-rc7-android-x86_64+ (root@localhost) (gcc
version 8.2.0 (Ubuntu 8.2.0-1ubuntu2))
Build fingerprint:
'Android-x86/android_x86/x86:8.1.0/OPM6.171019.030.B1/cwhuang0618:userdebug/test-keys'
Revision: '0'
ABI: 'x86'
pid: 2899, tid: 2899, name: zygote >>> zygote <<<
signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 0xec8
eax ebx f0274a40 ecx 01e0 edx 0ec8
On Tue, Jul 31, 2018 at 10:43 AM Luck, Tony wrote:
>
> If I just revert bfd40eaff5ab ("mm: fix vma_is_anonymous() false-positives")
> then ia64 boots again.
Ok, so it's not just the ashmem thing.
I think I'll do an rc8 with the revert, just so that we'll have some
time to figure this out. It's o
On Tue, Jul 31, 2018 at 08:03:28PM +0300, Kirill A. Shutemov wrote:
> But it's not the only issue unfortunately. Tony reported issue with
> booting ia64 with the patch. I have no clue why. I rechecked everything
> ia64-specific and looks fine to me. :-/
If I just revert bfd40eaff5ab ("mm: fix vma_
On Tue, Jul 31, 2018 at 09:29:22AM -0700, Linus Torvalds wrote:
> On Mon, Jul 30, 2018 at 11:40 PM Amit Pundir wrote:
> >
> > This ashmem change ^^ worked too.
>
> Ok, let's go for that one and hope it's the only one.
>
> John, can I get a proper commit message and sign-off for that ashmem chang
On Tue, Jul 31, 2018 at 9:29 AM, Linus Torvalds
wrote:
> On Mon, Jul 30, 2018 at 11:40 PM Amit Pundir wrote:
>>
>> This ashmem change ^^ worked too.
>
> Ok, let's go for that one and hope it's the only one.
>
> John, can I get a proper commit message and sign-off for that ashmem change?
Will do.
On Mon, Jul 30, 2018 at 11:40 PM Amit Pundir wrote:
>
> This ashmem change ^^ worked too.
Ok, let's go for that one and hope it's the only one.
John, can I get a proper commit message and sign-off for that ashmem change?
Kirill - you mentioned that somebody reproduced a problem on x86-64
too. I
On Tue, Jul 31, 2018 at 09:29:27AM +0300, Kirill A. Shutemov wrote:
> On Mon, Jul 30, 2018 at 06:01:26PM -0700, Linus Torvalds wrote:
> > On Mon, Jul 30, 2018 at 2:53 PM Hugh Dickins wrote:
> > >
> > > I have no problem with reverting -rc7's vma_is_anonymous() series.
> >
> > I don't think we nee
On Tue, Jul 31, 2018 at 12:10:06PM +0530, Amit Pundir wrote:
> On Tue, 31 Jul 2018 at 09:55, John Stultz wrote:
> >
> > On Mon, Jul 30, 2018 at 8:26 PM, Hugh Dickins wrote:
> > > On Mon, 30 Jul 2018, Linus Torvalds wrote:
> > >> On Mon, Jul 30, 2018 at 2:53 PM Hugh Dickins wrote:
> > >> >
> > >>
On Tue, 31 Jul 2018 at 09:55, John Stultz wrote:
>
> On Mon, Jul 30, 2018 at 8:26 PM, Hugh Dickins wrote:
> > On Mon, 30 Jul 2018, Linus Torvalds wrote:
> >> On Mon, Jul 30, 2018 at 2:53 PM Hugh Dickins wrote:
> >> >
> >> > I have no problem with reverting -rc7's vma_is_anonymous() series.
> >>
On Mon, Jul 30, 2018 at 06:01:26PM -0700, Linus Torvalds wrote:
> On Mon, Jul 30, 2018 at 2:53 PM Hugh Dickins wrote:
> >
> > I have no problem with reverting -rc7's vma_is_anonymous() series.
>
> I don't think we need to revert the whole series: I think the rest are
> all fairly obvious cleanups
On Mon, Jul 30, 2018 at 8:26 PM, Hugh Dickins wrote:
> On Mon, 30 Jul 2018, Linus Torvalds wrote:
>> On Mon, Jul 30, 2018 at 2:53 PM Hugh Dickins wrote:
>> >
>> > I have no problem with reverting -rc7's vma_is_anonymous() series.
>>
>> I don't think we need to revert the whole series: I think the
On Mon, 30 Jul 2018, Linus Torvalds wrote:
> On Mon, Jul 30, 2018 at 2:53 PM Hugh Dickins wrote:
> >
> > I have no problem with reverting -rc7's vma_is_anonymous() series.
>
> I don't think we need to revert the whole series: I think the rest are
> all fairly obvious cleanups, and shouldn't reall
On Mon, Jul 30, 2018 at 2:53 PM Hugh Dickins wrote:
>
> I have no problem with reverting -rc7's vma_is_anonymous() series.
I don't think we need to revert the whole series: I think the rest are
all fairly obvious cleanups, and shouldn't really have any semantic
changes.
It's literally only that
On Mon, 30 Jul 2018, Linus Torvalds wrote:
> On Mon, Jul 30, 2018 at 6:01 AM Kirill A. Shutemov
> wrote:
> >
> > I think I missed vma_set_anonymous() somewhere, but I fail to see where.
>
> Honestly, by now we just need to revert that commit.
>
> It's not even clear that it was a good idea to b
On Mon, Jul 30, 2018 at 6:01 AM Kirill A. Shutemov wrote:
>
> I think I missed vma_set_anonymous() somewhere, but I fail to see where.
Honestly, by now we just need to revert that commit.
It's not even clear that it was a good idea to begin with. The rest of
the commits were cleanups, this one w
On Mon, 30 Jul 2018 at 18:31, Kirill A. Shutemov wrote:
>
> On Mon, Jul 30, 2018 at 12:17:46PM +0530, Amit Pundir wrote:
> > On Mon, 30 Jul 2018 at 03:39, Linus Torvalds
> > wrote:
> > >
> > > So unless something odd happens, this should be the last rc for 4.18.
> > >
> > > Nothing particularly o
On Sun, Jul 29, 2018 at 03:09:05PM -0700, Linus Torvalds wrote:
> So unless something odd happens, this should be the last rc for 4.18.
>
> Nothing particularly odd happened this last week - we got the usual
> random set of various minor fixes all over. About two thirds of it is
> drivers - networ
On Mon, Jul 30, 2018 at 12:17:46PM +0530, Amit Pundir wrote:
> On Mon, 30 Jul 2018 at 03:39, Linus Torvalds
> wrote:
> >
> > So unless something odd happens, this should be the last rc for 4.18.
> >
> > Nothing particularly odd happened this last week - we got the usual
> > random set of various m
On Mon, 30 Jul 2018 at 03:39, Linus Torvalds
wrote:
>
> So unless something odd happens, this should be the last rc for 4.18.
>
> Nothing particularly odd happened this last week - we got the usual
> random set of various minor fixes all over. About two thirds of it is
> drivers - networking, stag
n"
Kirill A. Shutemov (3):
mm: introduce vma_init()
mm: use vma_init() to initialize VMAs on stack and data segments
mm: fix vma_is_anonymous() false-positives
Li Wang (1):
zswap: re-check zswap_is_full() after do zswap_shrink()
Linus Torvalds (2):
squashfs: be more
On Wed, 25 Jul 2018 12:40:26 -0700
Kees Cook wrote:
> On Tue, Jul 24, 2018 at 12:24 AM, Martin Schwidefsky
> wrote:
> > On Tue, 24 Jul 2018 09:15:58 +0200
> > Christian Borntraeger wrote:
> >
> >> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
> >> > On Mon, 23 Jul 2018 16:17:22 -0700
>
On Tue, Jul 24, 2018 at 12:24 AM, Martin Schwidefsky
wrote:
> On Tue, 24 Jul 2018 09:15:58 +0200
> Christian Borntraeger wrote:
>
>> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
>> > On Mon, 23 Jul 2018 16:17:22 -0700
>> > Linus Torvalds wrote:
>> >
>> >> On Mon, Jul 23, 2018 at 2:23 PM Gue
On 07/24/2018 09:24 AM, Martin Schwidefsky wrote:
> On Tue, 24 Jul 2018 09:15:58 +0200
> Christian Borntraeger wrote:
>
>> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
>>> On Mon, 23 Jul 2018 16:17:22 -0700
>>> Linus Torvalds wrote:
>>>
On Mon, Jul 23, 2018 at 2:23 PM Guenter Roe
On Tue, 24 Jul 2018 09:15:58 +0200
Christian Borntraeger wrote:
> On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
> > On Mon, 23 Jul 2018 16:17:22 -0700
> > Linus Torvalds wrote:
> >
> >> On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
> >>>
>
> Martin - can we just re
On 07/24/2018 08:18 AM, Martin Schwidefsky wrote:
> On Mon, 23 Jul 2018 16:17:22 -0700
> Linus Torvalds wrote:
>
>> On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
>>>
Martin - can we just remove the
select HAVE_GCC_PLUGINS
from the s390 Kconfig f
On Mon, 23 Jul 2018 16:17:22 -0700
Linus Torvalds wrote:
> On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
> >
> > >
> > > Martin - can we just remove the
> > >
> > > select HAVE_GCC_PLUGINS
> > >
> > > from the s390 Kconfig file (or perhaps add "if BROKEN" or something to
> > >
On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
>
> >
> > Martin - can we just remove the
> >
> > select HAVE_GCC_PLUGINS
> >
> > from the s390 Kconfig file (or perhaps add "if BROKEN" or something to
> > disable it).
> >
> > Because if it's not getting fixed, it shouldn't be exposed
On Mon, Jul 23, 2018 at 2:23 PM Guenter Roeck wrote:
>
> My patch is also at
>
> https://patchwork.ozlabs.org/patch/937283/
Ah, ok, so that just adds the forward-declaration of 'struct page' in
the right global namespace.
Anyway, I'll just re-order the includes as I suggested, which I think
is t
On Mon, Jul 23, 2018 at 01:56:15PM -0700, Linus Torvalds wrote:
> Adding davem for the sparc issue, Martin for the s390 one.
>
> On Mon, Jul 23, 2018 at 1:46 PM Guenter Roeck wrote:
> >
> > The s390 gcc plugins related build error reported previously has not really
> > been fixed; after feedback
From: Linus Torvalds
Date: Mon, 23 Jul 2018 13:56:15 -0700
> Hmm. I assume it's
>
> arch/sparc/include/asm/cacheflush_32.h
>
> that wants a forward-declaration of 'struct page', and doesn't include
> any header files.
>
> The fix is presumably to move the
>
>#include
>
> in drivers
Adding davem for the sparc issue, Martin for the s390 one.
On Mon, Jul 23, 2018 at 1:46 PM Guenter Roeck wrote:
>
> The s390 gcc plugins related build error reported previously has not really
> been fixed; after feedback from the s390 maintainers, suggesting that it
> won't get fixed in 4.18, I d
On Sun, Jul 22, 2018 at 02:23:39PM -0700, Linus Torvalds wrote:
> So this was the week when the other shoe dropped ... The reason the
> two previous rc releases were so nice and small was that David hadn't
> sent me much networking fixes, and they came in this week.
>
Build results:
tota
mm: use helper functions for allocating and freeing vm_area structs
mm: make vm_area_dup() actually copy the old vma data
mm: make vm_area_alloc() initialize core fields
Linux 4.18-rc6
Liran Alon (1):
KVM: VMX: Mark VMXArea with revision_id of physical CPU even
when eV
Linus,
The following changes since commit 786b71f5b754273ccef6d9462e52062b3e1f9877:
Merge tag 'nds32-for-linus-4.17-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/greentime/linux (2018-05-28
05:25:57 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/vir
RDMA/uverbs: Fix slab-out-of-bounds in ib_uverbs_ex_create_flow
RDMA/uverbs: Don't fail in creation of multiple flows
Linus Torvalds (1):
Linux 4.18-rc5
Lucas Stach (1):
drm/etnaviv: bring back progress check in job timeout handler
Masahiro Yamada (3):
kbuil
et/smc: fix up merge error with poll changes
autofs: rename 'autofs' module back to 'autofs4'
Fix up non-directory creation in SGID directories
Linux 4.18-rc4
Lyude Paul (3):
drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c
drm/amdgpu
1):
drm/amdgpu: fix UBSAN: Undefined behaviour for amdgpu_fence.c
Leonard Crestez (1):
iio: mma8452: Fix ignoring MMA8452_INT_DRDY
Linus Torvalds (3):
checkpatch: remove warning for 'old' sta...@kernel.org address
Revert changes to convert to ->poll_mask() and
ols/power turbostat: add optional APIC X2APIC columns
tools/power turbostat: version 18.06.20
Li RongQing (1):
net: propagate dev_get_valid_name return code
Linus Torvalds (2):
proc: fix missing final NUL in get_mm_cmdline() rewrite
Linux 4.18-rc2
Linus Walleij (1):
Linus,
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the Git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm tags/for-linus
for you to fetch changes up to
Hi Linus,
Please pull the following kselftest fixes update for Linux 4.18-rc2
This Kselftest fixes update for Linux 4.18-rc2:
- Fixes new sparc64 adi driver test compile errors on non-sparc systems.
- Fixes config fragment for sync framework for improved test coverage.
- Fixes several tests to
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20180604 was the first linux-next after
the merge window opened.)
Commits in v4.18-rc1 (relative to v4.17): 11594
Commits in next-20180604:
You may think it's still Saturday for me, and that I should give you
one more day of merge window to send in some last-minute pull
requests, but I know better. I'm in Japan, and it's Sunday here. Plus
I hope to spend much of this Sunday on a boat (assuming the swells
allow it), so I'm closing the
Hi Linus,
Please pull the following Kselftest update 2 for 4.18-rc1
This second Kselftest update for Linux 4.18-rc1:
- fixes a signedness bug in cgroups test
- adds ppc support for kprobe args tests
diff is attached.
thanks,
-- Shuah
On Tue, Jun 5, 2018 at 12:03 AM, Shuah Khan wrote:
> Hi Rafael,
Hi Shuah,
> If it isn't too late, please pull this update. A fix came in last
> week to refine the cpupower monitor command.
>
> This cpupower update for 4.18-rc1 consists of two minor fixes.
>
> diff is attached.
Pulled, thanks!
Hi Rafael,
If it isn't too late, please pull this update. A fix came in last
week to refine the cpupower monitor command.
This cpupower update for 4.18-rc1 consists of two minor fixes.
diff is attached.
thanks,
-- Shuah
The foll
63 matches
Mail list logo
