ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: ksummit-discuss@lists.linuxfoundation.org,
	Amir Goldstein <amir73il@gmail.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Linux kernel SMB server (CIFSD)
Date: Wed, 24 Jul 2019 17:03:47 +0900	[thread overview]
Message-ID: <20190724080347.GA12744@jagdpanzerIV> (raw)
In-Reply-To: <20190724055226.GA15444@jagdpanzerIV>

On (07/24/19 14:52), Sergey Senozhatsky wrote:
> On (05/30/19 01:59), Theodore Ts'o wrote:
> > From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
[..]
> To extend the topic with some discussion points:
> 
> - We are facing a rather familiar problem. Basically, SMB2 CHANGE_NOTIFY
>   [1] is something what fsnotify normally does, except that we can't use
>   it in cifsd kernel module. I see that NFS guys had [2] same issues some
>   time ago.
> 
>   So the question is - how to do fs notify style monitoring in a kernel
>   module (nfsd, cifsd)? Any chance the kernel can start exporting fsnotify
>   symbols?

I even looked at LSM hooks, because they do what we need - invoke
creat, open, truncate, chmod, chown, unlink, callbacks. But, first,
I do realize that LSM was not meant to be used as some sort of fsnotify
replacement, and, second, LSM symbols are not exported anyway :)

	-ss

  reply	other threads:[~2019-07-24  8:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  5:59 Theodore Ts'o
2019-07-24  5:52 ` Sergey Senozhatsky
2019-07-24  8:03   ` Sergey Senozhatsky [this message]
2019-07-24 10:50     ` Amir Goldstein
2019-07-24 10:55       ` Jeff Layton
2019-07-25  5:00         ` Sergey Senozhatsky
2019-07-30 17:01           ` Jan Kara
2019-07-31  3:09             ` Sergey Senozhatsky
2019-07-30 16:55         ` Jan Kara
2019-07-24 11:28       ` Sergey Senozhatsky
2019-07-24 16:42       ` Al Viro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190724080347.GA12744@jagdpanzerIV \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox