This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Failure in syscall.open probe

From: David Smith <dsmith at redhat dot com>
To: Arkady <arkady dot miasnikov at gmail dot com>
Cc: systemtap at sourceware dot org
Date: Wed, 30 Aug 2017 09:18:10 -0500
Subject: Re: Failure in syscall.open probe
Authentication-results: sourceware.org; auth=none
References: <CANA-60r00vRO+TtYhWL6TqS-A2We_ZBVVbUuMA+bOdRXOGx9cA@mail.gmail.com> <CANA-60oheK2zf742ts6DikqYzuYrOjbxqzpCLh7rhb0Y920bTQ@mail.gmail.com> <CANA-60qB62x6Uaibw7SVa2pWO6gRGTs6FuzugXxKdM=k3SN=YQ@mail.gmail.com> <CANA-60r415_H_YaYQhgDXPjj97jru0ouf=iy5z58LtTUPX=Nyg@mail.gmail.com> <CANA-60qXJLi_sUS1ure=zytCfuawWa-Qdz2a5a_C2zWOQ-NuPw@mail.gmail.com> <CANA-60oKogWr5jewx_emnC_N9WaQ8oX2C6gykJVPODx+x=FJNA@mail.gmail.com> <CAKFOr-b-LJy2bvi50OF8A6doFW_gW27j9PQd4R9OAL+v2SzqZQ@mail.gmail.com> <CANA-60pDknsnrHYS1edBJ3nXMw-ZiVcgigmgR2mtd7MPtFWO3Q@mail.gmail.com> <CANA-60qLBg4Pze+VFOnHS7J8zQUBaVwaWZpQ77AH1JZ1PyX43w@mail.gmail.com> <CANA-60pDmqGx8+tmPNw_OzBQ0Q7pBbbhZCePwMg-iAsy8ugrvw@mail.gmail.com> <CANA-60q7pd0c7RdghMK_akV7q3aM9gpGVFoC7QwOjmx9r2HU6A@mail.gmail.com> <CAKFOr-YPK_0=R++4Y+h4ORebRXDPkTN+POSK9Z+6kbsK3Uyd6A@mail.gmail.com> <CAKFOr-bPfoyByu5brSgfRJ4xHwwMh3wpzBc6J7pwEVHE79Y_8w@mail.gmail.com> <CANA-60oxBqf78K1m1rVmHM+JZPwTrssL_R+wyNZY-ZZUyocPoQ@mail.gmail.com>

On Tue, Aug 29, 2017 at 11:44 AM, Arkady <arkady.miasnikov@gmail.com> wrote:
> On Tue, Aug 29, 2017 at 7:05 PM, David Smith <dsmith@redhat.com> wrote:
>> I've checked that patch in as commit cd8837d56. Let me know if you
>> still see that "scheduling while atomic" bug.
>>
>
> What is the policy for back port of patches in the SystemTap project?
> For example, will release 3.1 be updated?

I'm not sure we really have a true policy for Fedora. We've back
ported things in the past when the patch was important enough, like
support for a newer kernel.

The biggest problem will be finding someone with the time to do the release.

-- 
David Smith
Principal Software Engineer
Red Hat

References:
- Failure in syscall.open probe
  - From: Arkady
- Re: Failure in syscall.open probe
  - From: Arkady
- Re: Failure in syscall.open probe
  - From: Arkady
- Re: Failure in syscall.open probe
  - From: Arkady
- Re: Failure in syscall.open probe
  - From: Arkady
- Re: Failure in syscall.open probe
  - From: Arkady
- Re: Failure in syscall.open probe
  - From: David Smith
- Re: Failure in syscall.open probe
  - From: Arkady
- Re: Failure in syscall.open probe
  - From: Arkady
- Re: Failure in syscall.open probe
  - From: Arkady
- Re: Failure in syscall.open probe
  - From: Arkady
- Re: Failure in syscall.open probe
  - From: David Smith
- Re: Failure in syscall.open probe
  - From: David Smith
- Re: Failure in syscall.open probe
  - From: Arkady

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]