From: Zdenek Kabelac <zkabelac@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Bug in dm_any_congested?
Date: Tue, 10 Nov 2015 15:39:04 +0100 [thread overview]
Message-ID: <56420188.7030406@redhat.com> (raw)
In-Reply-To: <CAEp_DRAcgXsjEPttRnVoDYo97ZeeQ6heiBZhGMkppOUxTnOxjA@mail.gmail.com>
Dne 10.11.2015 v 14:14 Boštjan Škufca @ Teon.si napsal(a):
> Hi all,
>
> (I am not sure if this is the right address for this bug, but dm_* is
> the first function listed in trace)
>
> this happened when I tried dd-ing LV, which resides on RAID10 sw
> storage, to network via netcat. The actual user-visible manifestation
> was segfault of dd that was used for reading.
>
> On first request the error reported was "unable to handle kernel NULL
> pointer dereference...", but on subsequent tries this changed to
> "general protection fault", see below.
>
> HW is a bit dated, but had no problems with it up to now, and SW raid
> is used here. Kernel was 4.2.4.
>
> Is this the right mlist for such bug?
Hi
Yes the issue is known - but source is not fully known.
I've opened public BZ: https://bugzilla.redhat.com/1279941
There is some potential fix - but unclear what it solves:
http://git.kernel.org/linus/ad5f498f610
Regards
Zdenek
next prev parent reply other threads:[~2015-11-10 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 13:14 Bug in dm_any_congested? Boštjan Škufca @ Teon.si
2015-11-10 14:39 ` Zdenek Kabelac [this message]
2015-11-10 15:02 ` Boštjan Škufca @ Teon.si
2015-11-10 17:27 ` Linux >= 4.2 dm_any_congested bug due to bad data from vfs/mm? [was: Bug in dm_any_congested?] Mike Snitzer
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=56420188.7030406@redhat.com \
--to=zkabelac@redhat.com \
--cc=dm-devel@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