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: <CAFLxGvwuZPPDbpvbHgPY2NuCvye_7FRAdxX7TirArNeP6nhkRw@mail.gmail.com>
Date:	Sat, 27 Jun 2015 20:10:55 +0200
From:	Richard Weinberger <richard.weinberger@...il.com>
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

On Sat, Jun 27, 2015 at 7:32 PM, Andreas Hartmann
<andihartmann@...19freenet.de> wrote:
> Hello!
>
> Given is a module like the following snippet running fine w/ Linux 4.0
> and ext4 fs - but doesn't work w/ Linux 4.1 because f->f_op->read is not
> defined any more (= NULL). Is this the intended behavior now?

See __vfs_read().
Your module most not rely on such internals.

-- 
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/