Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755297AbbF0SLE (ORCPT ); Sat, 27 Jun 2015 14:11:04 -0400 Received: from mail-vn0-f47.google.com ([209.85.216.47]:45094 "EHLO mail-vn0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753198AbbF0SK5 (ORCPT ); Sat, 27 Jun 2015 14:10:57 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 27 Jun 2015 20:10:55 +0200 Message-ID: Subject: Re: f_op->read seems to be always NULL since Linux 4.1 From: Richard Weinberger To: Andreas Hartmann Cc: LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 643 Lines: 19 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(). 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/