All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vacek <neelx.g@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Bernhard Landauer <bernhard@manjaro.org>,
	Ralf Mardorf <ralf.mardorf@alice-dsl.net>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: firefix core dump with linux 5.0.3_rt1-2
Date: Mon, 8 Apr 2019 22:35:46 +0200	[thread overview]
Message-ID: <CAA7rmPFTru+e2A8Uc04U+TExodJ=4pywWAC7cyfoncMCvKNg4A@mail.gmail.com> (raw)
In-Reply-To: <20190408195740.lxyiolx3xzypgoyx@linutronix.de>

On Mon, Apr 8, 2019 at 9:57 PM Sebastian Andrzej Siewior
<bigeasy@linutronix.de> wrote:
>
> On 2019-04-08 21:33:55 [+0200], Daniel Vacek wrote:
> > On Mon, Apr 8, 2019 at 7:31 PM Sebastian Andrzej Siewior
> > <bigeasy@linutronix.de> wrote:
> > >
> > > On 2019-03-29 09:38:33 [+0100], Bernhard Landauer wrote:
> > > >
> > > > > How do I reproduce this?
> > > >
> > > > For me this happens reliably when I launch a fresh instance of ff and it
> > > > automatically tries to restore tabs of the previous session.
> > > > Alternatively, when I select 'Restore Previous Session' from the menu.
> > >
> > > Does this help?
> >
> > >From an uninvolved lurker, how is this supposed to change a thing?
>
> on RT
>   local_irq_disable() + spin_lock() != spin_lock_irq()

Nah, the rt_mutex... I always fall into this trap :-/

> > Moreover, I'd say the original version is better readable.
>
> how so? You remove the irq/irq_save() from a lock and put a local_irq_()
> in front of it. Is the only purpose is to avoid enabling/disabling twice
> in a row?

What I meant is that it's two different locks so it's easier to see
that you a) disable interrupts and then b) do the work with the locks.
But yeah, you would have to change this to
local_irq_{dis,en}able_nort() to achieve what you did here. Still I'd
argue that doing this would be clearer to document the intention.
Anyways, please disregard. I'll back to lurking...

--nX

> > --nX
>
> Sebastian

  reply	other threads:[~2019-04-08 20:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28  9:29 firefix core dump with linux 5.0.3_rt1-2 Bernhard Landauer
2019-03-28 10:21 ` Sebastian Andrzej Siewior
2019-03-28 10:55 ` Ralf Mardorf
2019-03-28 11:30   ` Bernhard Landauer
2019-03-28 12:00     ` Sebastian Andrzej Siewior
2019-03-28 12:10       ` Bernhard Landauer
2019-03-28 12:13       ` Bernhard Landauer
2019-03-28 22:18       ` Bernhard Landauer
2019-03-28 22:25         ` Bernhard Landauer
2019-03-28 23:56           ` Bernhard Landauer
2019-03-29  8:34             ` Sebastian Andrzej Siewior
2019-03-29  8:38               ` Bernhard Landauer
2019-04-08 15:30                 ` Sebastian Andrzej Siewior
2019-04-08 19:33                   ` Daniel Vacek
2019-04-08 19:57                     ` Sebastian Andrzej Siewior
2019-04-08 20:35                       ` Daniel Vacek [this message]
2019-04-10  7:23                   ` Bernhard Landauer
2019-04-10  7:27                     ` Bernhard Landauer
2019-04-10  8:55                       ` Bernhard Landauer
2019-04-10  8:59                         ` Sebastian Andrzej Siewior
2019-04-25 10:43                           ` Sebastian Andrzej Siewior
2019-03-28 12:08     ` Ralf Mardorf

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='CAA7rmPFTru+e2A8Uc04U+TExodJ=4pywWAC7cyfoncMCvKNg4A@mail.gmail.com' \
    --to=neelx.g@gmail.com \
    --cc=bernhard@manjaro.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=ralf.mardorf@alice-dsl.net \
    /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.