Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1176277 > unrolled thread

Re: [!GIT PULL] kdbus for 4.2

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [!GIT PULL] kdbus for 4.2 Andy Lutomirski <luto@amacapital.net> - 2015-07-03 02:40 +0200
    Re: [!GIT PULL] kdbus for 4.2 Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2015-07-03 17:30 +0200
      Re: [!GIT PULL] kdbus for 4.2 Richard Weinberger <richard@nod.at> - 2015-07-03 18:30 +0200
    Re: [!GIT PULL] kdbus for 4.2 Andy Lutomirski <luto@amacapital.net> - 2015-07-03 18:30 +0200

#1176277 — Re: [!GIT PULL] kdbus for 4.2

On Fri, Jun 26, 2015 at 12:36 PM, Tom Gundersen <teg@jklm.no> wrote:
> On Fri, Jun 26, 2015 at 9:33 PM, Andy Lutomirski <luto@amacapital.net> wrote:
>> What's a good distro on which to poke at a full running system?
>
> Fedora Rawhide is probably currently your best bet.

I won't swear that all of the problems I'm seeing are 100% kdbus'
fault, but Rawhide, updated today, has serious problems with the kdbus
branch in Greg's char-misc tree.

Problem 1: Booting a kdbus-enabled kernel (CONFIG_KDBUS=y) causes gdm
to bail saying "oops, something went wrong" or whatever the useless
standard error message is.

I can work around problem 1 by booting with kdbus=1, but that's not
okay.  Unless this is limited to just some narrow range of Rawhide
versions, I don't think the kernel gets to make changes that break
userspace like that.  Maybe this is a kernel issue, not a user issue,
in which case it's not a big deal as long as it gets fixed.

Problem 2: Running 'sudo mount /mnt/share' from a terminal hangs the
whole graphical session hard.  This is repeatable.  /mnt/share is
virtfs, but I doubt that matters.

If I build exactly the same sources but set CONFIG_KDBUS=n, all is well.

I suspect that there are multiple issues here:

1. The current state of systemd's --disable-kdbus could be buggy.
kdbusfs still gets mounted but isn't set up and then things break.

2. mount generates a bunch of dbus traffic.  Apparently on the latest
char-misc kdbus tree with the latest Rawhide, it blows up somehow.

That's all from me until next week.

--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1176666

On Fri, Jul 03, 2015 at 10:53:57AM +0200, Richard Weinberger wrote:
> On Fri, Jul 3, 2015 at 10:43 AM, David Herrmann <dh.herrmann@gmail.com> wrote:
> > Hi
> >
> > On Fri, Jul 3, 2015 at 2:39 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> >> Problem 1: Booting a kdbus-enabled kernel (CONFIG_KDBUS=y) causes gdm
> >> to bail saying "oops, something went wrong" or whatever the useless
> >> standard error message is.
> >>
> >> I can work around problem 1 by booting with kdbus=1, but that's not
> >> okay.  Unless this is limited to just some narrow range of Rawhide
> >> versions, I don't think the kernel gets to make changes that break
> >> userspace like that.  Maybe this is a kernel issue, not a user issue,
> >> in which case it's not a big deal as long as it gets fixed.
> >
> > You're saying booting with the same kernel but kdbus not compiled in works?
> >
> >> Problem 2: Running 'sudo mount /mnt/share' from a terminal hangs the
> >> whole graphical session hard.  This is repeatable.  /mnt/share is
> >> virtfs, but I doubt that matters.
> >
> > This is triggered by running through pam from outside the gfx-session
> > but on a shared VT. It's not directly related to kdbus, though. It's
> > fixed in systemd-git. As a workaround, you can remove pam_systemd from
> > the sudo/su pam config.
> 
> Just because I'm starring right now at similar issues, how can I run
> systemd-git?
> I fear to use a plain "make && make install" as I don't want to break my
> distro's package management and I want to make sure that nothing from the
> currently installed systemd influences the system.

Use your distro's package management system to build a new systemd
package  based on just adding the single big patch diff from the last
release to the git head, or pick individual ones.  But really, this
isn't a kernel issue, you know how to build userspace distro packages...

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1176714

Am 03.07.2015 um 17:27 schrieb Greg Kroah-Hartman:
> On Fri, Jul 03, 2015 at 10:53:57AM +0200, Richard Weinberger wrote:
>> On Fri, Jul 3, 2015 at 10:43 AM, David Herrmann <dh.herrmann@gmail.com> wrote:
>>> Hi
>>>
>>> On Fri, Jul 3, 2015 at 2:39 AM, Andy Lutomirski <luto@amacapital.net> wrote:
>>>> Problem 1: Booting a kdbus-enabled kernel (CONFIG_KDBUS=y) causes gdm
>>>> to bail saying "oops, something went wrong" or whatever the useless
>>>> standard error message is.
>>>>
>>>> I can work around problem 1 by booting with kdbus=1, but that's not
>>>> okay.  Unless this is limited to just some narrow range of Rawhide
>>>> versions, I don't think the kernel gets to make changes that break
>>>> userspace like that.  Maybe this is a kernel issue, not a user issue,
>>>> in which case it's not a big deal as long as it gets fixed.
>>>
>>> You're saying booting with the same kernel but kdbus not compiled in works?
>>>
>>>> Problem 2: Running 'sudo mount /mnt/share' from a terminal hangs the
>>>> whole graphical session hard.  This is repeatable.  /mnt/share is
>>>> virtfs, but I doubt that matters.
>>>
>>> This is triggered by running through pam from outside the gfx-session
>>> but on a shared VT. It's not directly related to kdbus, though. It's
>>> fixed in systemd-git. As a workaround, you can remove pam_systemd from
>>> the sudo/su pam config.
>>
>> Just because I'm starring right now at similar issues, how can I run
>> systemd-git?
>> I fear to use a plain "make && make install" as I don't want to break my
>> distro's package management and I want to make sure that nothing from the
>> currently installed systemd influences the system.
> 
> Use your distro's package management system to build a new systemd
> package  based on just adding the single big patch diff from the last
> release to the git head, or pick individual ones.  But really, this
> isn't a kernel issue, you know how to build userspace distro packages...

I hoped some distros already offer such a package. Maybe Fedora?
Building packages is no fun nor trivial.

And IMHO this belongs here as systemd is the only user of kdbus and
kernel folks may want to give it a try.

Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1176711

On Jul 3, 2015 1:43 AM, "David Herrmann" <dh.herrmann@gmail.com> wrote:
>
> Hi
>
> On Fri, Jul 3, 2015 at 2:39 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> > Problem 1: Booting a kdbus-enabled kernel (CONFIG_KDBUS=y) causes gdm
> > to bail saying "oops, something went wrong" or whatever the useless
> > standard error message is.
> >
> > I can work around problem 1 by booting with kdbus=1, but that's not
> > okay.  Unless this is limited to just some narrow range of Rawhide
> > versions, I don't think the kernel gets to make changes that break
> > userspace like that.  Maybe this is a kernel issue, not a user issue,
> > in which case it's not a big deal as long as it gets fixed.
>
> You're saying booting with the same kernel but kdbus not compiled in works?
>

Yes, exactly.

The bad boot gets a couple warnings about dbus names getting lost or
something like that.

> > Problem 2: Running 'sudo mount /mnt/share' from a terminal hangs the
> > whole graphical session hard.  This is repeatable.  /mnt/share is
> > virtfs, but I doubt that matters.
>
> This is triggered by running through pam from outside the gfx-session
> but on a shared VT. It's not directly related to kdbus, though. It's
> fixed in systemd-git. As a workaround, you can remove pam_systemd from
> the sudo/su pam config.
>

I'll try on Monday.  Or maybe someone will build a new systemd on Rawhide :)

--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web