Ksummit-Discuss Archive on lore.kernel.org
 help / color / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: ksummit-discuss@lists.linuxfoundation.org,
	Amir Goldstein <amir73il@gmail.com>,
	Jeff Layton <jlayton@kernel.org>,
	Trond Myklebust <trondmy@gmail.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Linux kernel SMB server (CIFSD)
Date: Wed, 31 Jul 2019 12:09:13 +0900
Message-ID: <20190731030913.GA5614@jagdpanzerIV> (raw)
In-Reply-To: <20190730170115.GK28829@quack2.suse.cz>

On (07/30/19 19:01), Jan Kara wrote:
> On Thu 25-07-19 14:00:59, Sergey Senozhatsky wrote:
> > On (07/24/19 06:55), Jeff Layton wrote:
> > > (cc'ing Trond)
> > > 
> > > Trond has been driving those patches more recently. He posted a revised
> > > set of them recently, and they still use fsnotify to detect unlink
> > > activity:
> > > 
> > > https://www.spinics.net/lists/linux-nfs/msg73692.html
> > 
> > Jan, do you have objections?
> > Would be great to have fsnotify export patch in linux-next, maybe.
> I have no objections to export bits of fsnotify to modules. After all
> kernel/audit_tree.c is another external user of the fsnotify bits, just it
> happens not to be modularized so there was never need for exports.

That's great. At least we can expect that fsnotify will be exported
at some point and can start playing with fsnotify-based smb2_notify

> Once NFS guys (or someone else) have something that is close to inclusion,
> I can push the export patch to my tree (just CC me, Amir, and fsdevel on the
> series).

OK, both OverlayFS and NFS have some plans for fsnotify, so let's see.

> I prefer not to export symbols for something that is out of tree
> and will not be getting upstream in a near future. After all the export
> patch is easy to carry in your tree if you need it.

Makes perfect sense.


  reply index

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
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 [this message]
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 publically 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:

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

  git send-email \
    --in-reply-to=20190731030913.GA5614@jagdpanzerIV \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=trondmy@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Ksummit-Discuss Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/ksummit-discuss/0 ksummit-discuss/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ksummit-discuss ksummit-discuss/ https://lore.kernel.org/ksummit-discuss \
	public-inbox-index ksummit-discuss

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git