linux-kernel - Re: problem with ending requests asynchronously in my block device driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 16 Dec 2007 04:23:06 -0500
From:	Jon Masters <jonathan@...masters.org>
To:	a_kumar <cable_plug2000@...oo.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: problem with ending requests asynchronously in my block device
	driver

On Sat, 2007-12-15 at 12:52 -0800, a_kumar wrote:

> I've a block device driver which does the following, 

Why not send the actual code?

> This code works fine with most of the kernel versions, but fails on some
> like , Linux 2.6.18-8.el5-xen 

You've provided no information. What we need:

*). A well formed report, complete with oops, panic, other output.
*). Description of how it "fails".

Note also that there is no upstream Linux "2.6.18-8.el5-xen" kernel.

There is a Red Hat Enterprise Linux kernel release with that revision
(this is the one that shipped in the GA RHEL5.0 kernel). You should
contact your vendor for support with their kernel if you are unable to
provide a well-formed bug report against an upstream kernel release.

Jon.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/