linux-kernel - Re: user-space command "ipcs" seems broken on 2.6.18.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9a8748490610300936m38b54afei1e77f1c88ceccec4@mail.gmail.com>
Date:	Mon, 30 Oct 2006 18:36:09 +0100
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Metathronius Galabant" <m.galabant@...glemail.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: user-space command "ipcs" seems broken on 2.6.18.1

On 30/10/06, Jesper Juhl <jesper.juhl@...il.com> wrote:
> On 30/10/06, Metathronius Galabant <m.galabant@...glemail.com> wrote:
> > > Can you identify the latest kernel where it works OK?
> >
> > I can't reproduce that behaviour on another SMP machine with the same
> > kernel-config for 2.6.18.1 (only storage and network device drivers
> > differ).
> > The affected one is a production machine I can't use to test, and
> > furthermore the only one I've got of that series.
> >
> Ok, can you then at least tell us what the latest kernel you have used
> that was OK was?
> Just to try and narrow things down a bit.
>
> > Has to wait until the weekend. Any remote clue so I know where to look?
>
> Well, with a simple good/bad test case like you have, the obvious
> thing to do would be to find a resonably new kernel that's good and
> one that's bad and then do a git bisection search to find the exact
> commit that broke things for you. Short of that, narrowing it down to
> a released version, a -rc or -git snapshot is also good.
>
> You could also start browsing through changelogs looking for changes
> to IPC and then try revert patches that look likely. But  git bisect
> is probably a lot easier.
>
Ohh and btw, testing the latest -rc (and/or -git snapshot) kernel is
also useful, to see if the bug has already been fixed in what is to
become 2.6.19 eventually.

-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/