linux-kernel - Re: [patch 4/6] ide: allow ide_dev_read_id() to be called from the IRQ context

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]

Message-Id: <200908072035.07754.bzolnier@gmail.com>
Date:	Fri, 7 Aug 2009 20:35:07 +0200
From:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 4/6] ide: allow ide_dev_read_id() to be called from the IRQ context

On Friday 07 August 2009 20:09:52 David Miller wrote:
> From: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
> Date: Fri, 7 Aug 2009 19:46:07 +0200
> 
> > I've been looking and I've seen you pushing non-trivial IDE bug-fix
> > patches with almost no wider hardware coverage to upstream (i.e. one
> > of my own patches which has been _explicitly_ marked as needing more
> > linux-next exposure)..

Please note that the above incident caused unexpected/urgent work for
me so I would very much prefer to avoid such things in the future..

> "When are the patches to be applied?"
> 
> "You're a hyprocrite for applying these patches without hardware
>  regression testing you said is necessary."
> 
> Ok, you're position is clear :-)

Those are your own words (not mine), same goes for interpretation.. :-)

> Anyways, the ide-next-2.6 tree is up on kernel.org for all to
> enjoy and test, I look forward to everyone's feedback.

Thanks!
--
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/