linux-kernel - Re: [PATCH 1/1] um: fix error return code in winch

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Yoe5/HwL9DXhaw7Z@dev-arch.thelio-3990X>
Date:   Fri, 20 May 2022 08:55:40 -0700
From:   Nathan Chancellor <nathan@...nel.org>
To:     Thorsten Leemhuis <regressions@...mhuis.info>
Cc:     Richard Weinberger <richard@....at>,
        Zhen Lei <thunder.leizhen@...wei.com>,
        Jeff Dike <jdike@...toit.com>,
        anton ivanov <anton.ivanov@...bridgegreys.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Eduard-Gabriel Munteanu <maxdamage@...din.ro>,
        linux-um <linux-um@...ts.infradead.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        regressions <regressions@...ts.linux.dev>
Subject: Re: [PATCH 1/1] um: fix error return code in winch_tramp()

On Fri, May 20, 2022 at 08:08:01AM +0200, Thorsten Leemhuis wrote:
> On 11.04.22 20:45, Richard Weinberger wrote:
> > ----- Ursprüngliche Mail -----
> >> Von: "Nathan Chancellor" <nathan@...nel.org>
> >> I attempted to print out the error code but it seems like there is no
> >> output in the console after "reboot: System halted". If I add an
> >> unconditional print right before the call to os_set_fd_block(), I see it
> >> during start up but I do not see it during shutdown. Is there some way
> >> to see that console output during shutdown?
> > 
> > I think in this case the easiest way is attaching gdb with a breakpoint.
> 
> I noticed this in my list of open regressions. It seems there wasn't any
> progress to get this regression fixed (please let me know in case I
> missed something), but I guess nobody considered it urgent which is
> likely not that much of a problem in this case.

Yes, sorry, I tried to get gdb to reveal something but I couldn't get it
to work then I had to move onto other work. We have worked around this
for the time being but it would still be nice to figure out what is
going on here; I am just not sure when I am going to have time to
participate in that process.

Cheers,
Nathan