Unresponsive upstream (bcache)

[Ian Pilcher]

I recently moved my Fedora 20 root filesystem to a bcache device, and I
discovered a bug (limitation?) that sometimes prevents my system from
booting properly.

I originally reported this problem to the bcache-devel mailing list on
July 18, and I followed up with a suggested fix/patch on July 22:

http://thread.gmane.org/gmane.linux.kernel.bcache.devel/2594

I also entered a kernel bug:

https://bugzilla.kernel.org/show_bug.cgi?id=80961

It's been more than a week since I first reported this issue, and I have
not received any response at all (other than a thread-jack about a
seemingly unrelated issue).

What is a good open-sourcer to do when patches are, apparently, not so
welcome?

[Kevin Fenzi]

On Mon, 28 Jul 2014 13:37:40 -0500
Ian Pilcher  wrote:
> I recently moved my Fedora 20 root filesystem to a bcache device, and
> I discovered a bug (limitation?) that sometimes prevents my system
> from booting properly.
>
> I originally reported this problem to the bcache-devel mailing list on
> July 18, and I followed up with a suggested fix/patch on July 22:
>
> http://thread.gmane.org/gmane.linux.kernel.bcache.devel/2594
>
> I also entered a kernel bug:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=80961
>
> It's been more than a week since I first reported this issue, and I
> have not received any response at all (other than a thread-jack about
> a seemingly unrelated issue).
>
> What is a good open-sourcer to do when patches are, apparently, not so
> welcome?

Well, sometimes people are busy and don't answer right away, so
patience is always good.

Failing that, you could also open a redhat bugzilla bug against the
kernel and see if they could help you route your patch to someone who
can apply it upstream or at least carry it in Fedora until it's fixed
upstream.

kevin

[Ian Pilcher]

On 07/28/2014 01:45 PM, Kevin Fenzi wrote:
> Failing that, you could also open a redhat bugzilla bug against the
> kernel and see if they could help you route your patch to someone who
> can apply it upstream or at least carry it in Fedora until it's fixed
> upstream.

Past experience tells me it would simply be CLOSED UPSTREAM.

[Pete Travis]

On Jul 28, 2014 8:09 PM, "Ian Pilcher"  wrote:
> On 07/28/2014 01:45 PM, Kevin Fenzi wrote:
> > Failing that, you could also open a redhat bugzilla bug against the
> > kernel and see if they could help you route your patch to someone who
> > can apply it upstream or at least carry it in Fedora until it's fixed
> > upstream.
>
> Past experience tells me it would simply be CLOSED UPSTREAM.
> --
>
> Ian Pilcher

My past experience is that the Fedora kernel maintainers are responsive and
helpful to an appropriate degree.  Good bug reports get good responses,
vague or ambiguous ones get a response that helps clarify, problems where
other components are involved get redirected.

If a bug gets CLOSED UPSTREAM I'd say there's a very high probability that
the issue is actually under development or has already dealt with. Upstream
might have dealt with the issue in a way that's different from the approach
in your patch - that doesn't mean your bug is dismissed offhand or that
submitting your patch isn't appreciated.

--Pete