public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Marciniszyn,
	Mike" <mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Nicholas Krause
	<xerofoify-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"Hefty,
	Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
	<hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH RESEND] qib:Fix concurrent access in the function, qib_init_iba6120_funcs
Date: Tue, 8 Mar 2016 15:04:22 -0500	[thread overview]
Message-ID: <56DF3046.20406@redhat.com> (raw)
In-Reply-To: <20160307204948.GI13396-2ukJVAZIZ/Y@public.gmane.org>

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

[ Dropping linux-kernel, they already know what I'm going to write here,
this is mainly for the linux-rdma folks ]

On 03/07/2016 03:49 PM, Leon Romanovsky wrote:
> On Mon, Mar 07, 2016 at 04:34:04PM +0000, Marciniszyn, Mike wrote:
>>> This fixes concurrent access in the function, qib_init_iba6120_funcs by locking
>>> around the calls to when setting up f_sendctrl and f_set_armlauch function
>>> pointers to the functions, sendctrl_6120_mod qib_set_6120_armlaunch due to
>>> these functions needing to have their caller to hold the spinlock that is part of
>>> the qib_ibport pointer they are using and due to the lock not being held by
>>> higher up functions in the caller stack we need to hold it in qib_init_iba6210 to
>>> avoid conncurrent access when setting up these function pointers.
>>>
>>
>> I'm not sure I agree.
>>
>> static struct pci_driver qib_driver = {
>>         .name = QIB_DRV_NAME,
>>         .probe = qib_init_one,
>>         .remove = qib_remove_one,
>>         .id_table = qib_pci_tbl,
>>         .err_handler = &qib_pci_err_handler,
>> };
>>
>> The only caller is the probe function, which naturally protects since the device cannot be used until the probe returns.
>>
>> Are you actually having an issue with this older version of a qib card?
> 
> IMHO no,
> The author is famous developer - Nick Krause [1].
> 
> [1]
> http://news.softpedia.com/news/Malevolent-Developer-Trolls-Linux-Kernel-Development-with-Lots-of-Broken-Patches-453709.shtml

Guys, please quit feeding the trolls.  I reviewed Nick's patches when I
first took this job.  After deciding that they had a > 50% wrongness
value (meaning, even though the patches are trivial, more than half of
them are *still* wrong on average), he is now in my killfile.  If you
truly feel the need to review his stuff, be aware you will have to
submit it yourself for me to even consider it as his patches aren't even
allowed on the patchworks server (not my doing, it was this way when I
took this job).


-- 
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
              GPG KeyID: 0E572FDD



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]

  parent reply	other threads:[~2016-03-08 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1457323126-19686-1-git-send-email-xerofoify@gmail.com>
     [not found] ` <1457323126-19686-1-git-send-email-xerofoify-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-07 16:34   ` [PATCH RESEND] qib:Fix concurrent access in the function, qib_init_iba6120_funcs Marciniszyn, Mike
     [not found]     ` <32E1700B9017364D9B60AED9960492BC25A7C169-RjuIdWtd+YbTXloPLtfHfbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-03-07 20:49       ` Leon Romanovsky
     [not found]         ` <20160307204948.GI13396-2ukJVAZIZ/Y@public.gmane.org>
2016-03-08 20:04           ` Doug Ledford [this message]
     [not found]             ` <56DF5CB0.4040004@gmail.com>
     [not found]               ` <56DF5CB0.4040004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-11  2:52                 ` Doug Ledford
     [not found]     ` <56DDD4B9.5070802@gmail.com>
     [not found]       ` <56DDD4B9.5070802-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-07 21:17         ` Marciniszyn, Mike

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=56DF3046.20406@redhat.com \
    --to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=xerofoify-Re5JQEeQqe8AvxtiuMwx3w@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