From: Or Gerlitz <ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
To: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Linux RDMA list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org
Subject: Re: Possible process deadlock in RMPP flow
Date: Thu, 24 Sep 2009 09:38:43 +0300 [thread overview]
Message-ID: <4ABB13F3.1060702@Voltaire.com> (raw)
In-Reply-To: <20090923172532.GA32223@mtls03>
Eli Cohen wrote:
> On Wed, Sep 23, 2009 at 09:08:28AM -0700, Sean Hefty wrote:
>> What kernel does 1.4.2 map to?
> I think OFED 1.4.2 is based on kernel 2.6.27 but they're using RHEL 5.3
Yes, the usual mess: ofed X is based on kernel Y1 but with some additions from kernel Y2 plus plenty of unreviwed and non-merged patches. Distro Z picks ofed X and the result is 99% unsupportable as Roland said. Somehow this ofed creature is still hanging around working on the the next damage its going to bring into this world (code name 1.5)
Eli, here's a little tip for you, I had the displeasure to resolve bunch of support cases originating from the fact that the below 2 years old commit missed some ofed version (sorry forgot the number...), maybe it would help you as well?
Under a normal setting, if this commit actually solves a bug being hit by many costumers, someone would have opened a distro bugzilla case saying, "please pick this commit for your kernel", the customers would have either wait for the next distro update or use a distro intermediate kernel. Currently, I understand that distros are picking ofed versions and that's it.
Or.
commit b61d92d8ae6aa13b17d1c31e69d123879cec2ee2
Author: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Date: Fri Nov 30 17:30:18 2007 -0800
IB/mad: Fix incorrect access to items on local_list
next prev parent reply other threads:[~2009-09-24 6:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 15:04 Possible process deadlock in RMPP flow Eli Cohen
2009-09-23 16:08 ` Sean Hefty
[not found] ` <7A32EEE20DF5432CADB60B8F8B1E0093-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-09-23 16:20 ` Hal Rosenstock
2009-09-23 17:25 ` Eli Cohen
2009-09-24 6:38 ` Or Gerlitz [this message]
[not found] ` <4ABB13F3.1060702-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2009-09-24 7:36 ` Eli Cohen
2009-09-24 15:53 ` Sean Hefty
[not found] ` <53F5ED0C557B4667B22A27A0459B800B-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-09-27 8:01 ` Eli Cohen
2009-10-04 7:04 ` Or Gerlitz
[not found] ` <4AC8BE74.3050200@mellanox.co.il>
[not found] ` <4AC8BE74.3050200-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
2009-10-19 20:30 ` Sean Hefty
[not found] ` <BFC792E8570C48B8981C34F913243887-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-10-20 6:06 ` [ewg] " Tziporet Koren
2009-10-20 7:48 ` Eli Cohen
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=4ABB13F3.1060702@Voltaire.com \
--to=ogerlitz-hkgkho2ms0fwk0htik3j/w@public.gmane.org \
--cc=eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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