public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What happened to this patch?  (Re: [BUG] panic after umount (biscted))
Date: Fri, 14 Dec 2007 09:03:49 +0100	[thread overview]
Message-ID: <20071214080348.GG19673@kernel.dk> (raw)
In-Reply-To: <E1J2yZg-0004aQ-Rn@closure.thunk.org>

On Thu, Dec 13 2007, Theodore Ts'o wrote:
> 
> I was going through my set of kernel patches that I've cherry picked on
> LKML for my private kernel, and I noticed this hasn't gotten merged into
> mainline yet.   The original thread was here:
> 
> 	 http://lkml.org/lkml/2007/10/27/61
> 
> and addressed a panic after a umount reported by Sebastian Siewior.  Was
> this addressed in some other way?

Yes, the below wasn't a proposal for inclusion, the problem got fixed
differently by commit 51fd77bd9f512ab6cc9df0733ba1caaab89eb957

-- 
Jens Axboe


      reply	other threads:[~2007-12-14  8:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-14  0:38 What happened to this patch? (Re: [BUG] panic after umount (biscted)) Theodore Ts'o
2007-12-14  8:03 ` Jens Axboe [this message]

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=20071214080348.GG19673@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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