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-next>] [day] [month] [year] [list]
Message-ID: <249860.22361.qm@web86911.mail.ukl.yahoo.com>
Date:	Sat, 7 Apr 2007 16:57:32 +0000 (GMT)
From:	JanuGerman <doublemalam@...oo.co.uk>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	linuxkernel <linux-kernel@...r.kernel.org>
Subject: Re: Two questions regarding Opening files within Kernel!

Thanks Jan for the response.


>struct dentry *foooobar = lookup_one_len("/foo/bar", current->fs->root);


But that gives me a dentry, where as file object is still not reachable. 

Question: I am currently using a function called fs.h/dentry_open which takes a "dentry", "vfsmount" object  and flag (usually RW i.e. 2), and gives me the file object. with  your suggested method, vfsmount is still not available. In this regard, any idea about a function, which gives directly the file object instead of dentry will be highly appreciated. 


OR,  (Kindly see the code below), i need some thing for "missing vfsmount".


    struct dentry *foooobar = lookup_one_len("/foo/bar", current->fs->root);
    struct file *file1 = dentry_open(foooobar, "missing vfsmount here",2)



Thanks,
JG


	
	
		
___________________________________________________________ 
New Yahoo! Mail is the ultimate force in competitive emailing. Find out more at the Yahoo! Mail Championships. Plus: play games and win prizes. 
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk 
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ