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] [day] [month] [year] [list]
Date:	Sun, 12 Dec 2010 08:45:39 -0800
From:	Greg KH <gregkh@...e.de>
To:	linux-kernel@...r.kernel.org
Subject: Re: fsnotify & sysfs

On Sun, Dec 12, 2010 at 01:42:47PM +0100, Rodolfo Giometti wrote:
> Hello,
> 
> I know that a sysfs file may be pollable but I'm asking to myself how
> it could be difficult adding notifying support also.
> 
> Maybe adding a call to the fsnotify subsystem within the
> sysfs_notify() function as follow can do the trick?

Perhaps, does that work?

> However my problem is how to get the struct dentry pointer needed by
> fsnotify_change() related to the struct sysfs_dirent pointer passed to
> sysfs_notify(). :(

Yup, that's a problem :(

> Can you please give me any advice about to solve it?
> 
> Another question: in file linux/fs/sysfs/file.c I see:
> 
>    #include <linux/fsnotify.h>
> 
> but none of its functions are called into file.c... maybe it's a
> mistake?

Possibly, but look at the patch that added that line, perhaps it was put
there for a reason.

thanks,

greg k-h
--
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