linux-kernel - file_inode() vs f

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAKqeN29hu55Q0qXioaZKAppK-aA68rCaDUFg2z2AvUSEnnyMDA@mail.gmail.com>
Date:	Mon, 7 Oct 2013 13:08:09 +0200
From:	Andre Richter <andre.o.richter@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: file_inode() vs f_mapping->host

Hi all,

in this thread ( https://lkml.org/lkml/2013/3/17/128 ), Al Viro argues
that file_inode() is not equal to f_mapping->host in certain cases.

I'm asking, because in arch/x86/kernel/msr.c, msr_seek() retrieves the
inode via f_mapping while one function later, msr_read() uses
file_inode().
Is this on purpose?

In general, how do I distinguish when to use what?

Thanks in advance,
Andre
--
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/