All of lore.kernel.org
 help / color / mirror / Atom feed
From: florin@iucha.net (Florin Iucha)
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] procfs bug exposed by cdev changes
Date: Tue, 27 May 2003 23:35:08 -0500	[thread overview]
Message-ID: <20030528043508.GQ3359@iucha.net> (raw)
In-Reply-To: <20030528003105.GD27916@parcelfarce.linux.theplanet.co.uk>

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

On Wed, May 28, 2003 at 01:31:05AM +0100, viro@parcelfarce.linux.theplanet.co.uk wrote:
> 	Patch follows.  It had fixed ALSA-triggered memory corruption here -
> what happens in vanilla 2.5.70 is that clear_inode() is not called when
> procfs character device inodes are freed.  That leaves a freed inode on
> a cyclic list, with obvious unpleasantness following when we try to traverse
> it (e.g. when unregistering a device).
> 
> 	Please, apply.  Folks who'd seen oopsen/memory corruption after
> ALSA access - please, check if that fixes all problems.

It works fine. The ALSA loads, plays and unloads without a problem.

Thank you,
florin

-- 

"NT is to UNIX what a doughnut is to a particle accelerator."

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-05-28  4:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28  0:31 [PATCH] procfs bug exposed by cdev changes viro
2003-05-28  4:35 ` Florin Iucha [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-28 18:06 Olivier NICOLAS
2003-05-28 18:18 ` Stian Jordet

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=20030528043508.GQ3359@iucha.net \
    --to=florin@iucha.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.