linux-ext4 - Re: simplify ext4_sb_read

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: <ZDuOB8We29IAYR/4@infradead.org>
Date:   Sat, 15 Apr 2023 22:56:23 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Christoph Hellwig <hch@....de>
Cc:     William McVicker <willmcvicker@...gle.com>,
        Theodore Ts'o <tytso@....edu>, linux-ext4@...r.kernel.org,
        "Stephen E. Baker" <baker.stephen.e@...il.com>,
        adilger.kernel@...ger.ca
Subject: Re: simplify ext4_sb_read_encoding regression

On Sun, Apr 16, 2023 at 07:47:42AM +0200, Christoph Hellwig wrote:
> We could do that, but it seems a bit ugly.  What prevents symbol_request
> from working properly for this case in your setup?

To anwer to myself - I guess we need something else than a plain
EXPORT_SYMBOL for everything that is used by
symbol_request.  Which would be a nice cleanly anyway - exports for
symbol_request aren't normal exports and should probably have a clear
marker just to stand out anyway.