From: Sebastian Parschauer <sebastian.riemer@profitbricks.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: 3.12.y: srcu warning during free_dev() with dm-multipath
Date: Mon, 22 Jun 2015 14:22:54 +0200 [thread overview]
Message-ID: <5587FE1E.5000503@profitbricks.com> (raw)
In-Reply-To: <5587E281.5030606@gmail.com>
On 22.06.2015 12:25, Zdenek Kabelac wrote:
> Dne 22.6.2015 v 10:55 Sebastian Parschauer napsal(a):
>> Really, no response? Again?
>>
>> Why doesn't that surprise me if sending a bug report to Red Hat not
>> using their kernel,... Thanks a lot! So this is how discrimination feels
>> like,...
>>
>
> Have you checked your problem exists in the latest upstream kernel ?
It likely doesn't. I can't roll out the latest greatest unstable
upstream kernel into a public IaaS cloud where I can see the problem
from time to time but in a test environment it's more difficult to
reproduce. We also have custom code running in different unrelated parts
which would have to be adapted.
> If you are resolving issue with kernel 3.12 - it's likely a thing for
> your distribution and its maintenance support?
We are our own distribution. So I'm just the distribution maintainer
asking the authors of a patch if that one could be related instead of
doing reverse engineering. Maintainers should have a feeling for their
code and also care for important fixes so that these find their way into
the stable trees - no matter which distribution.
Maybe that's the difference between homebrew FOSS and commercial FOSS.
But there are upstream kernel maintainers who do care for linux-stable.
I'd like to mention md maintainer Neil Brown here.
> Upstream (and this is upstream ml) is close to release 4.1 kernel - so
> you are fixing couple years old issue? What kind of action do you expect ?
Just a hint at which patches to look at.
You maintain a 3.10 kernel for RHEL 7. That one is also old and not
latest upstream.
I'll try the patch.
Cheers,
Sebastian
>> On 17.06.2015 18:26, Sebastian Parschauer wrote:
>>> Hi dm developers,
>>>
>>> we hit the srcu warning in cleanup_srcu_struct() when removing
>>> dm-multipath devices. We run v3.12.40 but there is no change compared to
>>> v3.12.44 in drivers/md/dm.c or kernel/srcu.c.
>>>
>>> Would the following upstream commit fix this?
>>>
>>> 63a4f06 dm: fix add_disk() NULL pointer due to race with free_dev()
>>>
>>> Thanks,
>>> Sebastian
>>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2015-06-22 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 16:26 3.12.y: srcu warning during free_dev() with dm-multipath Sebastian Parschauer
2015-06-22 8:55 ` Sebastian Parschauer
2015-06-22 10:25 ` Zdenek Kabelac
2015-06-22 12:22 ` Sebastian Parschauer [this message]
2015-06-22 14:21 ` 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=5587FE1E.5000503@profitbricks.com \
--to=sebastian.riemer@profitbricks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.