linux-kernel - Re: f_op->read seems to be always NULL since Linux 4.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 for Android: free password hash cracker in your pocket

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

Message-ID: <558FA47E.9010000@nod.at>
Date:	Sun, 28 Jun 2015 09:38:38 +0200
From:	Richard Weinberger <richard@....at>
To:	Andreas Hartmann <andihartmann@...19freenet.de>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: f_op->read seems to be always NULL since Linux 4.1

Am 28.06.2015 um 08:36 schrieb Andreas Hartmann:
> On Sat, Jun 27, 2015 at 8:10 PM, Richard Weinberger wrote:
>> On Sat, Jun 27, 2015 at 7:32 PM, Andreas Hartmann
>> <andihartmann@...19freenet.de> wrote:
> [...]
>> See __vfs_read().
>> Your module most not rely on such internals.
> 
> Thanks for your hint to the function which exists since 3.19.
> 
> Is there a site out there which lists all relevant changes done for each kernel version and the recommendations how to correctly handle them?

There is no such site.
The only way do deal with the ever changing in-kernel ABI is
bringing your code mainline.

Thanks,
//richard
--
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/