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 for Android: free password hash cracker in your pocket

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

Message-ID: <e9597cbc-cabb-facf-deb6-662d40cf16a3@leemhuis.info>
Date:   Fri, 20 May 2022 08:08:01 +0200
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Richard Weinberger <richard@....at>,
        Nathan Chancellor <nathan@...nel.org>
Cc:     Thorsten Leemhuis <regressions@...mhuis.info>,
        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 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. Hence I'm moving this to
the back-burner:

#regzbot backburner: special case and UML a leisure pursuit for the
maintainer

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.