linux-kernel - Re: [PATCH] libata: Prepare for hard drives w/ non-512 sector sizes

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:	Wed, 8 Apr 2009 13:13:59 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	linux-ide@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] libata: Prepare for hard drives w/ non-512 sector sizes

On Wed, Apr 08, 2009 at 03:08:14PM -0400, Jeff Garzik wrote:
> Matthew Wilcox wrote:
> >?!  Are you referring to the one incident where you asked me if I had
> >any patches for 2.6.30, I pointed at the TRIM patches and you quibbled
> >that I hadn't reposted the updates, only a git tree?
> 
> On multiple occasions.  You're the only one I have to poke to get 
> updates on pending libata patches, in some cases, patches that really 
> should have gone upstream long ago.

I send patches and get no feedback from the maintainer (you).  So I
work on other things instead.  The 4k sector size support is largely
theoretical anyway, given that every _SATA_ vendor I've heard from is
planning on doing 4k physical / 512 byte logical sectors.  SAS is a
different matter, but is irrelevant to this series of patches.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/