public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Meitner <lkml@kwax.hn.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] inotify for 2.6.11
Date: Sun, 10 Apr 2005 11:16:33 -0500	[thread overview]
Message-ID: <d3bjbr$anq$1@sea.gmane.org> (raw)
In-Reply-To: <1109961444.10313.13.camel@betsy.boston.ximian.com>

Robert Love wrote:
> Below is inotify, diffed against 2.6.11.
> 
> I greatly reworked much of the data structures and their interactions,
> to lay the groundwork for sanitizing the locking.  I then, I hope,
> sanitized the locking.  It looks right, I am happy.  Comments welcome.
> I surely could of missed something.  Maybe even something big.
> 
> But, regardless, this release is a huge jump from the previous, fixing
> all known issues and greatly improving the locking.
> 

Inotify 0.22 severly destabilized my 2.6.11 system when it was in use.
The system would get into a state where it was unable to spawn new
processes, the desktop would hang, and the only way to shut down would
be to do a hard reset. This only happened when inotify was in use after
gamin started up.  I was only able to get the following out of the
logs(not every time though):

c017b901
Modules linked in: radeon deflate zlib_deflate twofish serpent aes_i586
blowfish sha256 sha1 crypto_null af_key parport_pc lp parport 8250_pci
8250 serial_core usbhid ohci_hcd ohci1394 ieee1394 yenta_socket
rsrc_nonstatic
suspend_text
CPU:    0
EIP:    0060:[inotify_ignore+49/224]    Not tainted VLI
EFLAGS: 00010246   (2.6.11.6-nx9005)
EIP is at inotify_ignore+0x31/0xe0
eax: 00000000   ebx: e88544e0   ecx: 00000000   edx: 00000000
esi: 00000000   edi: e88544e0   ebp: e8760000   esp: e8761f20
ds: 007b   es: 007b   ss: 0068
Process gam_server (pid: 6640, threadinfo=e8760000 task=ed19e060)
Stack: e88544e8 000000f6 e88544e0 fffffff2 fffffff7 c017bace e88544e0
000000f6
       00000004 000000f6 00000292 00000000 08098e54 80045102 fffffff7
c01685a8
       e5d584c0 80045102 08098e54 c0456118 00000000 e5d584c0 c0168785
e5d584c0
Call Trace:
 [inotify_ioctl+286/288] inotify_ioctl+0x11e/0x120
 [do_ioctl+104/128] do_ioctl+0x68/0x80
 [vfs_ioctl+101/464] vfs_ioctl+0x65/0x1d0
 [sys_ioctl+69/144] sys_ioctl+0x45/0x90
 [syscall_call+7/11] syscall_call+0x7/0xb
Code: 10 89 5c 24 08 89 74 24 0c 8b 7c 24 18 ff 4f 28 0f 88 95 03 00 00
8b 44 24 1c 89 44 24 04 8d 47 08 89 04 24 e8 11 89 0b 00 89 c6 <ff> 40
10 ff 47 28 0f 8e 81 03 00 00 85 f6 b8 ea ff ff ff 74 6e

Thanks.


  parent reply	other threads:[~2005-04-10 17:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 18:37 [patch] inotify for 2.6.11 Robert Love
2005-03-04 19:11 ` [patch] inotify for 2.6.11-mm1 Robert Love
2005-03-07  1:19   ` Christoph Hellwig
2005-03-07  1:38     ` Andrew Morton
2005-03-07 21:27     ` [patch] inotify for 2.6.11-mm1, updated Robert Love
2005-03-08  4:40       ` Christoph Hellwig
2005-03-08  4:50         ` Robert Love
2005-03-08 17:08           ` Robert Love
2005-03-04 21:38 ` [patch] inotify for 2.6.11 Timothy R. Chavez
2005-03-04 21:40   ` Robert Love
2005-03-06  0:04 ` Christoph Hellwig
2005-03-06  0:40   ` Robert Love
2005-03-07  1:23     ` Christoph Hellwig
2005-03-07  4:33       ` Robert Love
2005-03-07 21:25 ` [patch] inotify for 2.6.11, updated Robert Love
2005-04-05  7:58 ` [patch] inotify for 2.6.11 Prakash Punnoor
2005-04-05 16:12   ` Robert Love
2005-04-05 17:20     ` Prakash Punnoor
2005-04-05 17:35       ` Robert Love
2005-04-05 22:09       ` Robert Love
2005-04-06  3:21       ` Adam Kropelin
2005-04-10 16:16 ` Erik Meitner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-07  3:13 Albert Cahalan
2005-03-08  1:00 ` Arnd Bergmann
     [not found] <3EqlI-2DI-59@gated-at.bofh.it>
     [not found] ` <3PRs6-89U-15@gated-at.bofh.it>
     [not found]   ` <3PYWC-636-7@gated-at.bofh.it>
     [not found]     ` <3Q0F6-7Ar-37@gated-at.bofh.it>
     [not found]       ` <3Q4z0-2tA-15@gated-at.bofh.it>
     [not found]         ` <pan.2005.04.06.00.53.44.705260@intel.com>
2005-04-06  1:21           ` Robert Love
     [not found] <3Q7wT-4HJ-11@gated-at.bofh.it>
     [not found] ` <3Q7wT-4HJ-13@gated-at.bofh.it>
     [not found]   ` <3Q7wT-4HJ-15@gated-at.bofh.it>
     [not found]     ` <3Q7wT-4HJ-17@gated-at.bofh.it>
     [not found]       ` <3Q7wT-4HJ-19@gated-at.bofh.it>
     [not found]         ` <3Q7wT-4HJ-21@gated-at.bofh.it>
     [not found]           ` <3Q7wT-4HJ-9@gated-at.bofh.it>
     [not found]             ` <pan.2005.04.08.01.37.42.462474@intel.com>
2005-04-08  1:52               ` Robert Love

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='d3bjbr$anq$1@sea.gmane.org' \
    --to=lkml@kwax.hn.org \
    --cc=linux-kernel@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