private final String name;
        private final int type;
        private final String scope;

        TestNetbiosName(String name, int type, String scope) {
            // Ensure names are uppercase and limited to 15 characters
            this.name = name != null && name.length() > 15 ? name.substring(0, 15).toUpperCase() : (name != null ? name.toUpperCase() : "");
            this.type = type;
            this.scope = scope;

            // Then
            assertEquals(107374182400L, fileFsFullSizeInfo.getCapacity()); // 100GB total
            assertEquals(10737418240L, fileFsFullSizeInfo.getFree()); // 10GB (quota limited)
        }

        @Test
        @DisplayName("Should handle typical Linux ext4 configuration")
        void shouldHandleTypicalExt4Configuration() throws SMBProtocolDecodingException {

 * imposes both obligations and limits on the client application.
 *
 * ### The response body must be closed.
 *
 * Each response body is backed by a limited resource like a socket (live network responses) or
 * an open file (for cached responses). Failing to close the response body will leak resources and
 * may ultimately cause the application to slow down or crash.
 *

   * time it is closed.
   *
   * The connection is implicit, and will generally relate to the last [connectionAcquired] event.
   *
   * This will usually be invoked only 1 time for a single [Call], exceptions are a limited set of
   * cases including failure recovery.
   *
   * Prior to OkHttp 4.3 this was incorrectly invoked when the client was ready to read the response
   * body. This was misleading for tracing because it was too early.

     *
     * - Any kind of Error from a listener. Even if we could distinguish that case (by exposing some
     * extra state from AbstractFuture), our options are limited: A call to setException() would be
     * a no-op. We could log, but if that's what we really want, we should modify
     * AbstractFuture.executeListener to do so, since that method would have the ability to continue

jcifs.smb.client.rdmaProvider=disni

# Witness
jcifs.smb.client.useWitness=true
jcifs.smb.client.witnessNotificationTimeout=5000
```

## Risk Assessment

### Technical Risks
1. **RDMA Complexity**: Limited Java RDMA support may require JNI
2. **Multi-Channel Synchronization**: Complex thread synchronization required
3. **Persistent Handle State**: Requires reliable state persistence mechanism

     * </ul>
     * <p>
     * The active profiles control various aspects of the build configuration including but not
     * limited to dependencies, plugins, properties, and build resources.
     *
     * @return a non-null, possibly empty list of active profiles for this project
     * @see Profile
     * @see #getEffectiveActiveProfiles()
     */

        br.addNotice("Too long boundary size so treats it as 404.");
        br.addItem("Advice");
        br.addElement("Against for CVE-2014-0050 (JVN14876762).");
        br.addElement("Boundary size is limited by Framework.");
        br.addElement("Too long boundary is treated as 404 because it's thought of as attack.");
        br.addElement("");
        br.addElement("While, you can override the boundary limit size");

      <artifactId>okio</artifactId>
      <version>1.3.0</version>
    </dependency>
    ```

 *  **Fix: improve parallelism of async requests.** OkHttp's Dispatcher had a
    misconfigured `ExecutorService` that limited the number of worker threads.
    If you're using `Call.enqueue()` this update should significantly improve
    request concurrency.

 *  **Fix: Lazily initialize the response cache.** This avoids strict mode

        byte[] buffer = createBasicNegotiateResponseBuffer();
        // Set SMB 3.1.1 dialect
        SMBUtil.writeInt2(0x0311, buffer, 4);
        // Set excessive negotiate context count (should be limited to 100)
        SMBUtil.writeInt2(1000, buffer, 6);
        // Set negotiate context offset to valid value
        SMBUtil.writeInt4(128, buffer, 60);