From: "J. Bruce Fields" <bfields@fieldses.org>
To: "David Härdeman" <david@hardeman.nu>
Cc: linux-nfs@vger.kernel.org, SteveD@redhat.com
Subject: Re: [PATCH 00/19] gssd improvements
Date: Wed, 10 Dec 2014 16:07:23 -0500 [thread overview]
Message-ID: <20141210210723.GG20235@fieldses.org> (raw)
In-Reply-To: <20141210204917.GA11396@hardeman.nu>
On Wed, Dec 10, 2014 at 09:49:17PM +0100, David Härdeman wrote:
> On Wed, Dec 10, 2014 at 03:35:11PM -0500, J. Bruce Fields wrote:
> >On Tue, Dec 09, 2014 at 06:40:40AM +0100, David Härdeman wrote:
> >> The following series converts gssd to use libevent and inotify instead
> >> of a handrolled event loop and dnotify. Lots of cleanups in the process
> >> (e.g. removing a lot of arbitrary limitations and fixed size buffers).
> >>
> >> All in all a nice reduction in code size (what can I say, I was bored).
> >
> >This code has been crying out for help for a while, thanks for taking a
> >look!
>
> :)
>
> >On dnotify/inotify: if I remember correctly, this was written before
> >inotify existed. So you're probably breaking compatibility with older
> >kernels, which we normally try not to do.
>
> Fair enough...but...there has to be some kind of reasonable limit to
> that. Like...unmaintained kernel versions with known CVEs...if an
> organization is *that* conservative...I kinda doubt they'd update
> nfs-utils either?
Personally I worry more about troubleshooting: RHEL4 user runs into nfs
problem that looks like something we fixed in recent nfs-utils, we might
like to be able to tell them just to try latest nfs-utils....
But at this point I think that's unlikely.
> >According to inotify(7):
> >
> > Inotify was merged into the 2.6.13 Linux kernel. The required
> > library interfaces were added to glibc in version 2.4.
> > (IN_DONT_FOLLOW, IN_MASK_ADD, and IN_ONLYDIR were added in
> > version 2.5.)
> >
> >So that's almost 10 years. In RHEL terms I think RHEL4 would be the
> >latest without inotify support.
> >
> >OK, maybe that's long enough.
>
> I should add that krb5 support was added on 13 January 2003,
> (commit e0594725b51b5253237ed11b8bf3cf9ab87d9d48)
> which corresponds to kernel version 2.5.57 or .58.
>
> 2.6.13 is from 29 August, 2005....so we'd kill support for that time
> span...
>
> >If there's an easy way to provide a fallback to dnotify, that would be
> >nice
>
> I think you and I have different ideas of the definition of the word
> "nice" :)
>
> >otherwise would you mind just adding a note about this somewhere?
> >(Maybe the gssd man page should say something like "this version of gssd
> >depends on inotify, introduced in kernel version 2.6.13...".)
>
> I could add that in a separate patch...both to the changelog and the man
> page.
That'd be fine, thanks.--b.
next prev parent reply other threads:[~2014-12-10 21:07 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 5:40 [PATCH 00/19] gssd improvements David Härdeman
2014-12-09 5:40 ` [PATCH 01/19] nfs-utils: cleanup daemonization code David Härdeman
2014-12-09 5:40 ` [PATCH 02/19] nfs-utils: gssd - merge gssd_main_loop.c and gssd.c David Härdeman
2014-12-09 5:40 ` [PATCH 03/19] nfs-utils: gssd - simplify some option handling David Härdeman
2014-12-09 5:41 ` [PATCH 04/19] nfs-utils: gssd - remove arbitrary GSSD_MAX_CCACHE_SEARCH limitation David Härdeman
2014-12-09 5:41 ` [PATCH 05/19] nfs-utils: gssd - simplify topdirs path David Härdeman
2014-12-09 5:41 ` [PATCH 06/19] nfs-utils: gssd - move over pipfs scanning code David Härdeman
2014-12-09 5:41 ` [PATCH 07/19] nfs-utils: gssd - simplify client dir " David Härdeman
2014-12-09 5:41 ` [PATCH 08/19] nfs-utils: gssd - use libevent David Härdeman
2014-12-09 5:41 ` [PATCH 09/19] nfs-utils: gssd - remove "close me" code David Härdeman
2014-12-09 5:41 ` [PATCH 10/19] nfs-utils: gssd - make the client lists per-topdir David Härdeman
2014-12-09 5:41 ` [PATCH 11/19] nfs-utils: gssd - keep the rpc_pipefs dir open David Härdeman
2014-12-09 5:41 ` [PATCH 12/19] nfs-utils: gssd - use more relative paths David Härdeman
2014-12-09 5:41 ` [PATCH 13/19] nfs-utils: gssd - simplify topdir scanning David Härdeman
2014-12-09 5:41 ` [PATCH 14/19] nfs-utils: gssd - simplify client scanning David Härdeman
2014-12-09 5:41 ` [PATCH 15/19] nfs-utils: gssd - cleanup read_service_info David Härdeman
2014-12-09 5:42 ` [PATCH 16/19] nfs-utils: gssd - change dnotify to inotify David Härdeman
2014-12-09 5:42 ` [PATCH 17/19] nfs-utils: gssd - further shorten some pathnames David Härdeman
2014-12-09 5:42 ` [PATCH 18/19] nfs-utils: gssd - improve inotify David Härdeman
2014-12-09 5:42 ` [PATCH 19/19] nfs-utils: gssd - simplify handle_gssd_upcall David Härdeman
2014-12-09 13:09 ` [PATCH 00/19] gssd improvements Jeff Layton
2014-12-09 13:52 ` David Härdeman
2014-12-09 14:58 ` Jeff Layton
2014-12-09 15:07 ` Simo Sorce
2014-12-09 19:55 ` David Härdeman
2014-12-10 11:52 ` Jeff Layton
2014-12-10 14:08 ` David Härdeman
2014-12-10 14:17 ` Jeff Layton
2014-12-10 14:31 ` David Härdeman
2014-12-10 14:34 ` Jeff Layton
2014-12-10 16:03 ` David Howells
2014-12-10 19:03 ` Jeff Layton
2014-12-10 20:55 ` David Härdeman
2014-12-10 23:44 ` Ian Kent
2014-12-10 23:21 ` Benjamin Coddington
2014-12-11 0:12 ` Ian Kent
2014-12-11 1:54 ` Benjamin Coddington
2014-12-11 3:21 ` Ian Kent
2014-12-11 11:45 ` Jeff Layton
2014-12-11 12:55 ` Ian Kent
2014-12-11 13:46 ` Jeff Layton
2014-12-11 22:31 ` Ian Kent
2014-12-11 19:32 ` J. Bruce Fields
2014-12-11 19:50 ` Jeff Layton
2014-12-11 19:55 ` J. Bruce Fields
2014-12-11 20:11 ` Jeff Layton
2014-12-11 20:38 ` J. Bruce Fields
2014-12-11 22:20 ` Ian Kent
2014-12-09 16:39 ` Steve Dickson
2014-12-09 20:22 ` David Härdeman
2014-12-09 21:13 ` Steve Dickson
2014-12-10 14:20 ` David Härdeman
2014-12-10 20:35 ` J. Bruce Fields
2014-12-10 20:49 ` David Härdeman
2014-12-10 21:07 ` J. Bruce Fields [this message]
2015-01-28 21:29 ` Steve Dickson
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=20141210210723.GG20235@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=david@hardeman.nu \
--cc=linux-nfs@vger.kernel.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