public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@karaya.com>
To: Oleg Drokin <green@namesys.com>
Cc: James Stevenson <james@stev.org>,
	linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] uml-patch-2.5.39
Date: Tue, 01 Oct 2002 13:19:36 -0500	[thread overview]
Message-ID: <200210011819.NAA02853@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Tue, 01 Oct 2002 11:44:54 +0400." <20021001114454.A27039@namesys.com>

green@namesys.com said:
> Here's what I need to apply before I can build bk-current with UML
> support. 

Applied, thanks.

> And then kernel mode fault at 0x5a5a5a5e 

Can you get a stack trace from that crash?

> Just before the crash it warns about winch_interrupt : read failed,
> errno = 9 fd 57 is losing SIGWINCH support 

This looks different.  Is it consistently the same file descriptor?  If so,
put a breakpoint on close and see who's closing it who isn't supposed to.

> @@ -863,6 +863,7 @@
>  			return(-EFAULT);
>  		return(0);
>  	}
> +	return -ENOTTY;
>  }

I did a check of some of the other block drivers, and they mostly seem to
do -EINVAL rather than -ENOTTY.  There was an oddball -ENOSYS, but I guess
I'll stick with -EINVAL.

				Jeff


  reply	other threads:[~2002-10-01 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 19:55 uml-patch-2.5.39 Jeff Dike
2002-09-30 20:26 ` [uml-devel] uml-patch-2.5.39 James Stevenson
2002-10-01  7:44   ` Oleg Drokin
2002-10-01 18:19     ` Jeff Dike [this message]
2002-10-01 18:38       ` Oleg Drokin
2002-10-02  5:54       ` Oleg Drokin

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=200210011819.NAA02853@ccure.karaya.com \
    --to=jdike@karaya.com \
    --cc=green@namesys.com \
    --cc=james@stev.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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