linux-kernel - Re: [patch 32/35 code-cleanup] reiserfs: rename p_s

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 30 Mar 2009 15:18:10 -0400
From:	Jeff Mahoney <jeffm@...e.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	ReiserFS Development List <reiserfs-devel@...r.kernel.org>
Subject: Re: [patch 32/35 code-cleanup] reiserfs: rename p_s_inode to inode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andi Kleen wrote:
> Jeff Mahoney <jeffm@...e.com> writes:
>> --- a/fs/reiserfs/file.c
>> +++ b/fs/reiserfs/file.c
>> @@ -137,17 +137,17 @@ static void reiserfs_vfs_truncate_file(s
>>  static int reiserfs_sync_file(struct file *p_s_filp,
>>  			      struct dentry *p_s_dentry, int datasync)
>>  {
>> -	struct inode *p_s_inode = p_s_dentry->d_inode;
>> +	struct inode *inode = p_s_dentry->d_inode;
>>  	int n_err;
>>  	int barrier_done;
> 
> Didn't you miss one here?

Nope. This renamed p_s_inode, and that's a p_s_dentry. That one gets
handled in reiserfs: rename p_._ variables.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAknRGvIACgkQLPWxlyuTD7ItdQCgiuVxsIJVzXv66VzTNuRmfF0n
VNgAoJZHYLAtS6mj4Uzxb2+WL/J5Pv+y
=fQ5U
-----END PGP SIGNATURE-----
--
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/