Re: f_op->read seems to be always NULL since Linux 4.1

2015-06-28 Thread Al Viro
On Sun, Jun 28, 2015 at 08:36:18AM +0200, Andreas Hartmann wrote: > On Sat, Jun 27, 2015 at 8:10 PM, Richard Weinberger wrote: > >On Sat, Jun 27, 2015 at 7:32 PM, Andreas Hartmann > > wrote: > [...] > >See __vfs_read(). > >Your module most not rely on such internals. > > Thanks for your hint to th

Re: f_op->read seems to be always NULL since Linux 4.1

2015-06-28 Thread Richard Weinberger
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 >> wrote: > [...] >> See __vfs_read(). >> Your module most not rely on such internals. > > Thanks for your hint to the function which

Re: f_op->read seems to be always NULL since Linux 4.1

2015-06-27 Thread 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 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 re

Re: f_op->read seems to be always NULL since Linux 4.1

2015-06-27 Thread Richard Weinberger
On Sat, Jun 27, 2015 at 7:32 PM, Andreas Hartmann 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().