mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Eric Paris <eparis@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.36-rc7
Date: Thu, 7 Oct 2010 18:15:53 +0100	[thread overview]
Message-ID: <201010071815.54303.tvrtko.ursulin@sophos.com> (raw)
In-Reply-To: <201010071710.46938.tvrtko.ursulin@sophos.com>

On Thursday 07 Oct 2010 17:10:46 Tvrtko Ursulin wrote:
> On Wednesday 06 Oct 2010 22:45:13 Linus Torvalds wrote:
> [snip]
>
> > And yes, that's probably as exciting as it gets, which is just fine by
> > me. This should be the last -rc, I'm not seeing any reason to keep
> > delaying a real release. There was still more changes to
> > drivers/gpu/drm than I really would have hoped for, but they all look
> > harmless and good. Famous last words.
>
> Hi Linus,
>
> Please see http://marc.info/?l=linux-kernel&m=128618485204253&w=2
>
> I have sent this proposed bugfix several times now but no one is picking it
> up and Eric seems to have disappeared. It would be suboptimal to release
> 2.6.36 with a core fanotify feature non-functional.

Unfortunately I have another showstopper. Sadly I missed it until now because
internally we were more worried of issues which were kind of direct problems
for us and I went to deep instead of spending more time reviewing it breath
first.

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=08ae89380a8210a9965d04083e1de78cb8bca4b1

Priority argument was dropped from the fanotify_init syscall, and since it is
a syscall once released it is set in stone. Without the priority argument, how
are multiple clients supposed to be ordered?

Co-existence between multiple clients was something which was supposed to be
designed in from the start. Use cases like hierarchical storage management,
anti-malware and content indexing should all be able to co-exist. Without a
priority argument I do not see how it can be assured HSM sees the perm event
before anti-malware, and content indexing after both of them? If there was any
discussion about dropping priority I missed it. :(

Tvrtko

Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom.
Company Reg No 2096520. VAT Reg No GB 348 3873 20.

  reply	other threads:[~2010-10-07 17:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 21:45 Linus Torvalds
2010-10-07  0:49 ` Stephen Rothwell
2010-10-08 15:05   ` James Bottomley
2010-10-07 16:10 ` Tvrtko Ursulin
2010-10-07 17:15   ` Tvrtko Ursulin [this message]
2010-10-07 17:33     ` Eric Paris
2010-10-07 18:07       ` Alan Cox
2010-10-07 17:49         ` Eric Paris
2010-10-08 12:06           ` Andreas Gruenbacher
2010-10-08 16:33             ` David Daney
2010-10-08 21:50               ` Andreas Gruenbacher
2010-10-08 21:59                 ` H. Peter Anvin
2010-10-11 22:13                   ` fanotify: disable fanotify syscalls Eric Paris
2010-10-08 16:38             ` Linux 2.6.36-rc7 Eric Paris
2010-10-08 21:45               ` Andreas Gruenbacher
2010-10-07 20:55       ` John Stoffel
2010-10-07 21:24         ` Eric Paris
2010-10-08 15:42           ` John Stoffel
2010-10-08 16:17             ` Tvrtko Ursulin
2010-10-08 16:41               ` Eric Paris
2010-10-18 11:01                 ` Tvrtko Ursulin
2010-10-08 16:54               ` John Stoffel
2010-10-08 21:03               ` Andreas Gruenbacher
2010-10-09  0:46                 ` John Stoffel
2010-10-07 19:28 ` Tejun Heo
2010-10-07 20:13   ` [dm-devel] " Milan Broz
2010-10-08 17:02     ` Tejun Heo
2010-10-10 11:56       ` Torsten Kaiser
2010-10-11 10:09       ` [PATCH wq#for-next] workqueue: fix HIGHPRI handling in keep_working() Tejun Heo

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=201010071815.54303.tvrtko.ursulin@sophos.com \
    --to=tvrtko.ursulin@sophos.com \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

Powered by JetHome