public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Maneesh Soni <maneesh@in.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Dipankar Sarma <dipankar@in.ibm.com>
Subject: Re: 2.4.13pre5aa1
Date: Mon, 22 Oct 2001 12:01:13 +0200	[thread overview]
Message-ID: <20011022120113.K8408@athlon.random> (raw)
In-Reply-To: <20011020194024.C10680@in.ibm.com>
In-Reply-To: <20011020194024.C10680@in.ibm.com>; from maneesh@in.ibm.com on Sat, Oct 20, 2001 at 07:40:24PM +0530

On Sat, Oct 20, 2001 at 07:40:24PM +0530, Maneesh Soni wrote:
> 
> In article <20011019061914.A1568@athlon.random> you wrote:
> 
> > Only in 2.4.13pre3aa1: 00_files_struct_rcu-2.4.10-04-1
> > Only in 2.4.13pre5aa1: 00_files_struct_rcu-2.4.10-04-2
> 
> Hello Andrea,
>  
> Please apply the following update for the rcu fd patch.
> This has fixes for two more bugs pointed by Dipankar.
>  
> 1. fs/file.c
>         in expand_fd_array new_fds is not freed if allocation for arg fails.
>  
> 2. fs/file.c
>         kmalloc for arg instead of *arg in expand_fd_array and expand_fdset

thanks for the update!! Applied.

Andrea

  reply	other threads:[~2001-10-22 10:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-20 14:10 2.4.13pre5aa1 Maneesh Soni
2001-10-22 10:01 ` Andrea Arcangeli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-21 18:41 2.4.13pre5aa1 khromy
2001-10-21 23:51 ` 2.4.13pre5aa1 Andrea Arcangeli
2001-10-20 14:18 2.4.13pre5aa1 Maneesh Soni
2001-10-19  7:14 2.4.13pre5aa1 Dipankar Sarma
2001-10-19  4:19 2.4.13pre5aa1 Andrea Arcangeli
2001-10-19  5:48 ` 2.4.13pre5aa1 Robert Love
2001-10-21 19:17 ` 2.4.13pre5aa1 jogi
2001-10-22  0:04   ` 2.4.13pre5aa1 Andrea Arcangeli
     [not found]   ` <Pine.LNX.4.33L.0110211749310.3690-100000@imladris.surriel.com>
2001-10-22 11:08     ` 2.4.13pre5aa1 jogi

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=20011022120113.K8408@athlon.random \
    --to=andrea@suse.de \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.com \
    /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