linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Wool <vitalywool@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Seth Jennings <sjenning@redhat.com>,
	Dan Streetman <ddstreet@ieee.org>,
	bugzilla-daemon@bugzilla.kernel.org,
	Linux-MM <linux-mm@kvack.org>,
	jagannathante@gmail.com
Subject: Re: [Bug 201603] New: NULL pointer dereference when using z3fold and zswap
Date: Tue, 6 Nov 2018 23:10:28 +0100	[thread overview]
Message-ID: <CAMJBoFOw1J3PYxTL7GBXmVW+tNBjdcGU+4FBh+vdf7aY0sv1ZA@mail.gmail.com> (raw)
In-Reply-To: <20181106134837.014c0bf61eb959e27f5edd0c@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]

Hi,
Den tis 6 nov. 2018 kl 22:48 skrev Andrew Morton <akpm@linux-foundation.org
>:

>
> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Fri, 02 Nov 2018 10:41:46 +0000 bugzilla-daemon@bugzilla.kernel.org
> wrote:
>
> > https://bugzilla.kernel.org/show_bug.cgi?id=201603
> >
> >             Bug ID: 201603
> >            Summary: NULL pointer dereference when using z3fold and zswap
> >            Product: Memory Management
> >            Version: 2.5
> >     Kernel Version: 4.18.16
> >           Hardware: All
> >                 OS: Linux
> >               Tree: Mainline
> >             Status: NEW
> >           Severity: high
> >           Priority: P1
> >          Component: Page Allocator
> >           Assignee: akpm@linux-foundation.org
> >           Reporter: jagannathante@gmail.com
> >         Regression: No
> >
> > Created attachment 279297
> >   --> https://bugzilla.kernel.org/attachment.cgi?id=279297&action=edit
> > dmesg log of crash
>
>
Basing on what I see in dmesg, it is highly likely to get fixed by
https://lkml.org/lkml/2018/11/5/726. Could you please apply/retest?

Best regards,
   Vitaly

> > This happens mostly during memory pressure but I am not sure how to
> trigger it
> > reliably. I am attaching the full log.
> >
> > This is the kernel commandline
> >
> > >BOOT_IMAGE=../vmlinuz-linux
> root=UUID=57274b3a-92ab-468e-b03a-06026675c1af rw
> > >rd.luks.name=92b4aeb2-fb97-45c1-8a60-2816efe5d57e=home
> resume=/dev/mapper/home
> > >resume_offset=42772480 acpi_backlight=video zswap.enabled=1
> zswap.zpool=z3fold
> > >zswap.max_pool_percent=5 transparent_hugepage=madvise
> scsi_mod.use_blk_mq=1
> > >vga=current initrd=../intel-ucode.img,../initramfs-linux.img
> >
> > I found this bug https://bugzilla.kernel.org/show_bug.cgi?id=198585 to
> be very
> > similar but the proposed fix has not been merged so I can't be sure if
> it will
> > fix the issue I am having.
> >
> > --
> > You are receiving this mail because:
> > You are the assignee for the bug.
>

[-- Attachment #2: Type: text/html, Size: 3529 bytes --]

      reply	other threads:[~2018-11-06 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-201603-27@https.bugzilla.kernel.org/>
2018-11-06 21:48 ` Andrew Morton
2018-11-06 22:10   ` Vitaly Wool [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMJBoFOw1J3PYxTL7GBXmVW+tNBjdcGU+4FBh+vdf7aY0sv1ZA@mail.gmail.com \
    --to=vitalywool@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=ddstreet@ieee.org \
    --cc=jagannathante@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=sjenning@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox