linux-kernel - Re: [PATCH] Rewrite the MAJOR() macro as a call to imajor().

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Pine.LNX.4.61.0705041008180.18504@yvahk01.tjqt.qr>
Date:	Fri, 4 May 2007 10:09:06 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	"Robert P. J. Day" <rpjday@...dspring.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Rewrite the MAJOR() macro as a call to imajor().


On May 3 2007 23:18, Andrew Morton wrote:
>>  	struct inode *i = file->f_mapping->host;
>> 
>> -	return i && S_ISBLK(i->i_mode) && MAJOR(i->i_rdev) == LOOP_MAJOR;
>> +	return i && S_ISBLK(i->i_mode) && imajor(i) == LOOP_MAJOR;
>>  }
>
>there's no runtime change, and I count a couple hundred MAJORs in the tree.

Why do we even have imajor() if all it does is calling the MAJOR()
macro?


Jan
-- 
-
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/