From: Richard Weinberger <richard@nod.at>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: f_op->read seems to be always NULL since Linux 4.1
Date: Sun, 28 Jun 2015 09:38:38 +0200 [thread overview]
Message-ID: <558FA47E.9010000@nod.at> (raw)
In-Reply-To: <558F95E2.7070303@01019freenet.de>
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@01019freenet.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
next prev parent reply other threads:[~2015-06-28 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 17:32 f_op->read seems to be always NULL since Linux 4.1 Andreas Hartmann
2015-06-27 18:10 ` Richard Weinberger
2015-06-28 6:36 ` Andreas Hartmann
2015-06-28 7:38 ` Richard Weinberger [this message]
2015-06-28 8:30 ` Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=558FA47E.9010000@nod.at \
--to=richard@nod.at \
--cc=andihartmann@01019freenet.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox