netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, drt@linux.ibm.com,
	ljp@linux.ibm.com, sukadev@linux.ibm.com
Subject: Re: [PATCH v2 net-next] ibmvnic: workaround QT Creator/libCPlusPlus segfault
Date: Fri, 22 Jan 2021 10:25:12 +0300	[thread overview]
Message-ID: <20210122072512.GA3854@localhost.localdomain> (raw)
In-Reply-To: <20210121184454.0ef91be3@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Thu, Jan 21, 2021 at 06:44:54PM -0800, Jakub Kicinski wrote:
> On Fri, 22 Jan 2021 01:07:39 +0300 Alexey Dobriyan wrote:
> > My name is Alexey and I've tried to use IDE for kernel development.
> > 
> > QT Creator segfaults while parsing ibmvnic.c which is annoying as it
> > will start parsing after restart only to crash again.
> > 
> > The workaround is to either exclude ibmvnic.c from list of project files
> > or to apply dummy ifdef to hide the offending code.
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1886548
> > 
> > Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> 
> That's a bug in QT Creator and whatever parsing it does/uses.
> 
> Sorry we can't take this patch, there is no indication that the kernel
> code is actually wrong here.

It is QtC bug. It will take ages for distros to pick up the fix
(which doesn't even exist probably).

  reply	other threads:[~2021-01-22  7:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 22:01 [PATCH net-next] ibmvnic: workaround QT Creator/libCPlusPlus segfault Alexey Dobriyan
2021-01-21 22:07 ` [PATCH v2 " Alexey Dobriyan
2021-01-22  2:44   ` Jakub Kicinski
2021-01-22  7:25     ` Alexey Dobriyan [this message]
2021-01-21 22:31 ` [PATCH " Andrew Lunn

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=20210122072512.GA3854@localhost.localdomain \
    --to=adobriyan@gmail.com \
    --cc=davem@davemloft.net \
    --cc=drt@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=ljp@linux.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=sukadev@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).