| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Files with non-ASCII names inaccessible after xfs_repair |
| From: | Michael Weissenbacher <mw@xxxxxxxxxxxx> |
| Date: | Thu, 16 Jan 2014 21:55:51 +0100 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20140115210803.GX3469@dastard> |
| References: | <20140113192732.GI3469@dastard> <0E45339E-04C4-4775-B6B0-FC55245B0AED@xxxxxxxxxxxx> <20140114022414.GM3469@dastard> <BE0C947E-37DE-4CA1-B120-59B95E1E8EB8@xxxxxxxxxxxx> <20140115015350.GR3469@dastard> <61E74CEF-8244-4E90-BA7D-91D54DADC3C1@xxxxxxxxxxxx> <20140115034803.GT3469@dastard> <1E5E569C-2E11-42A1-A771-89D4800BC412@xxxxxxxxxxxx> <20140115063722.GW3469@dastard> <52D6AF1A.8010604@xxxxxxxxxxx> <20140115210803.GX3469@dastard> |
| User-agent: | Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 |
Hi! That's easy actually, since ASCII is a 7-bit code it can only contain char values between 0-127 or in other words the highest bit must not be set in any char. But probably this strict check could break other stuff.The utf-8 patches add a "is this valid utf-8" check to all the operations that care. We could probably do that for the ASCII-CI stuff if you can define what ASCII means.... cheers, Michael |
| Previous by Date: | xfs: blocked for more than 120 seconds, Ivan Novick |
|---|---|
| Next by Date: | Your real fund, COMPENSATION OFFICE |
| Previous by Thread: | Re: Files with non-ASCII names inaccessible after xfs_repair, Dave Chinner |
| Next by Thread: | RE: Files with non-ASCII names inaccessible after xfs_repair, Shaun Gosse |
| Indexes: | [Date] [Thread] [Top] [All Lists] |